Community mailing list archives
Re: Odoo in a distributed (MULTIMASTER replication) environment?by
Ray, db level sync could do the trick, but app level sync sounds wiser:Some sort of idoo2odoo connector, or maybe just some reporei based Python scripts ran by crons.
No dia 01/12/2016, às 16:38, Ray Carnes <firstname.lastname@example.org
Thanks for the replies.
The angle I will be pursuing for now is:
A prospect has been testing it between several Odoo 9 instances in my lab.
500,000 invoice records and 400,000 res_partner records.
Notes from them: It is lightweight on the WAN connection. It will catch-up if disconnected for days. It is simple to set up and use (unlike Slony). Right now it is an extension but is proposed to be built into the next Postgres release or so, so it appears fairly serious.
On Mon, Nov 28, 2016 at 8:47 AM, Ray Carnes <email@example.com
Has anyone implemented “distributed” (ideally loosely coupled logical multi-master replication) environment?
A complete Odoo stack at each site, with eventual replication of data between sites of SOME tables (perhaps partners and some crm data) – not EVERYTHING. I’m just getting started understanding requirements, but each Odoo stack could be implemented as a company in a multi-company environment. The companies would carry on mostly independently, but want to access CRM data across companies.
Bucardo? – Postgres-BDR?
Can you point me to anything to help me start to understand how to do this? What might be the ‘gotcha’ things to consider. Is anyone doing this? What questions should I be trying to answer?
Senior Odoo Consultant
Greater Los Angeles, UNITED STATES.
The information in this email (including any accompanying document) is
intended only for the recipient and any distribution of the same is prohibited.