Hibernate 分布式二级缓存提供“免费”功能复制？
我一直在尝试 Hibernate 3.6，我想知道所提供的 infinispan 分布式缓存的功能。
我需要在主站点和灾难恢复站点之间进行数据库复制。
虽然可以配置 PostgreSQL 进行复制，但我认为这可能会导致相同的数据从主站点发送到灾难恢复站点两次。我的应用程序预计会有很多更新，因此需要牢记这一点。由于这将通过受限的 WAN 链接进行，因此感觉会发送大量数据，但这看起来不是一个好主意。
是否可以将 infinispan 配置为在两个站点之间进行复制，以便底层数据库不需要自行复制？ 如果是这样，怎么办？带宽强度如何？
I have been experimenting with Hibernate 3.6 and I am wondering about the capabilities of the provided infinispan distributed cache.
I have a requirement to have database replication between my main site and my disaster recovery site.
While it is possible to configure PostgreSQL to replicate, I am thinking that it might cause the same data to be sent twice from the main to the DR site. My application is expected to have a lot of updates, so that's something to keep in mind. Since this would be over a constrained WAN link, it feels like a lot of data would be sent and that just doesn't look like a good idea.
Can infinispan be configured to replicate between the two sites such that the underlying database doesn't need to ever be replicated itself?
If so, how? How bandwith intensive would it be?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Postgresql>=9.0有很好的复制功能，使用它。如果您有大量更新，则不应将缓存复制到灾难恢复中心。除了恢复所需的数据之外，您不应复制任何内容。
灾备中心==一些备份>>负载均衡等
这取决于。您可以手动刷新数据，可以将刷新模式设置为自动、提交等。
Postgresql >=9.0 has very good replication, use it. You shouldn't replicate cache to DR center, if You have a lot of updates. You shouldn't replicate enything other than data needed to recovery.
DR Center == some backup <> load balancing etc.
It depends. You can flush data manually, you can set flush mode to auto,commit etc.