BDR is best when you have a need of multi-master environment like a distributed database paradigm where you have a need of writing/reading to/from local masters let's say masters in NY, London, China, India etc.. And it uses pglogical to achieve this with a globally managed transaction XID's. It needs to be properly tested how it handles conflicts in a heavy oltp workload application.
If you only need high availability for a heavy oltp application, a well set active passive model of streaking replication backed by repmgr where writes are only hitting primary and reads on standby will help. Otherwise you can also consider citusdata..
Note: I am not an advocate of any vendors, my comments are purely based on my experience and I love Postgresql the way it is!
Regards,
Rijo Roy
On Fri, 12 Apr 2019, 6:34 am soumitra bhandary, <soumitra.bhandary@xxxxxxxxxxx> wrote:
To ensure zero down time.
Sent from my iPhoneIt very much depends upon your use case. Why you want a multi master implementation?
On Thu, Apr 11, 2019 at 8:03 PM soumitra bhandary <soumitra.bhandary@xxxxxxxxxxx> wrote:
Hi ,
Can anyone suggest me for large OLTP application which sort of replication is suitable BDR or master slave replication with synchronous and asynchronous node and REPMGR enabled.
Can BDR handle real-time conflicts arises due to high network latency or Dataintegrity conflicts?? Please suggest
Sent from my iPhone
