Hibernate 的集群感知缓存与 WebSphere Application Server 结合使用
标题来自以下链接： 将 Spring 和 Hibernate 与 WebSphere Application Server 结合使用< /a>
想知道这是否仍然是一个真实的陈述？
我有兴趣将应用程序从使用 IBM DistributedMap 和 DistributedObjectCache 迁移到类似 ehCache 或 osCache 的东西。到目前为止，从我对 IBM 的两个缓存模型的阅读来看，我没有看到可以在哪里缓存查询。我可能会遗漏一些东西，如果是这样，请引导我到正确的位置。我们使用的是 WAS 7.x。
在集群环境中使用 ehCache 或 osCache 是否有任何疑问？
The title comes from the following link: Using Spring and Hibernate with WebSphere Application Server
Wonder if that is still a true statement?
I am interested in moving the application from using IBM DistributedMap and DistributedObjectCache to something along the lines of ehCache or osCache. From my reading so far of the two cache models from IBM I do not see where I can cache a query. I might be missing something and if so please direct me to the right spot. We are using WAS 7.x.
Any concerns using either ehCache or osCache in a clustered environment?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我假设您指的是“集成二级缓存”部分附近框中的语句。这种情况我会先跟IBM确认。有关 IBM 官方支持的任何信息都应直接来自他们，而不是来自 StackOverflow 中的某个人；-)
从缓存提供者的角度来看，Hibernate 如何使用它并不相关，因为 2L 实体缓存和查询缓存* 的配置是相同的。因此，只需配置缓存提供程序，Hibernate 就会在后端使用它来进行 2L 缓存和查询缓存。请注意，您仍然需要告诉 Hibernate 要缓存哪些实体以及要缓存哪些查询。最后一条建议：在使用之前了解缓存。大多数人认为他们理解，但他们惊讶地发现查询缓存会减慢速度而不是提高性能...
[*] 该语句不是 100% 正确，因为您可能仍然需要创建/配置不同的缓存区域，但它并不是真正特定于查询缓存或 2L 实体缓存...它只是一个缓存配置。
I assume you meant the statement in the box near to the "Integrating a second-level cache" section. In this case, I would first confirm with IBM. Any information about official support from IBM should come directly from them, not from someone in StackOverflow ;-)
From the cache provider's point of view, how Hibernate will use it isn't relevant, as the configuration is the same for either 2L entity caching and query caching*. So, just configure the cache provider and Hibernate will take care of using it for the backend for 2L caching and query caching. Just note that you still need to tell Hibernate which entities to cache and which queries to cache. One last advice: understand caching before using. Most people think that they understand, but they get surprised to see that a query caching slows things down instead of improving the performance...
[*] that statement is not 100% true, as you may still need to create/configure the different cache regions, but it's not really specific to query caching or 2L entity caching... it's just a cache configuration.