Geek Answers Handbook

Replication scheme proposal for my use case?

I am working on an application that runs on multiple clients that communicate with the same main MySQL database. In addition, we have a web application that uses the same MySQL database.

Due to latency issues, all clients will have to run their own local MySQL database, which should be a copy of the main MySQL database. The web application remains using the main MySQL database.

Clients read only from table A and write to table B. The web application writes both tables A and B.

How to set up a replication scheme that ensures data consistency? Customers must remain offline for a long period of time. Is this possible using MySQL, or am I better off looking at something like CouchDB? CouchDB seems to explicitly support this according to the website:

it allows users and servers to access and update the same shared data while disconnected, and then bidirectionally repeat these changes later

(from: http://couchdb.apache.org/docs/overview.html )

0
source share
1 answer

CouchDB has the semantics you need if you manage to move away from MySQL.

" ". MVCC, .. .

+2

More articles:


All Articles