与 RDBMS 无关的事务复制子系统的注意事项
我正在开发一个与 RDBMS 无关的事务复制器(主要通过 ODBC 启动,尽管我个人首选的 RDBMS 将是 PostgreSQL),以保证两个数据库中的数据一致。
这与 TIBCO Rendezvous 类似,但不针对 Oracle,并且(可能)非-商业的。
我已经考虑过替代方案,例如使用简单的 消息队列,但是如果两个语言环境中的用户/进程更新如果您同时(或在事务可以复制之前)复制同一个对象,您仍然面临权限和“谁是对的”问题。
需要牢记哪些主要考虑因素,尤其是环境中极有可能发生冲突的因素?
I am working on a RDBMS-agnostic (primarily via ODBC to start, though my personal preferred RDBMS is going to be PostgreSQL) transaction replicator for guaranteeing data in two databases is consistent.
This would be in similar vein to TIBCO Rendezvous, but not targeted at Oracle, and (likely) non-commercial.
I have considered alternatives such as using a simple message queue, but if users/processes in two locales update the same object at the same time (or before a transaction can replicate), you are still left with the issue of authority and "who's right".
What are primary considerations to keep in mind, especially concerning the high potential for conflicts in the environment?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
有一些解决方案,但我不知道现实与营销广告之间的差距到底有多大。
(更新:2015-03-13:似乎不再支持Postgres)
There are some solutions out there, but I have no idea how big the gap between reality and the marketing advertising actually is.
(update: 2015-03-13: does not seem to support Postgres any longer)