Need to decide which mechanism to opt

Question

0.00/5 (No votes)

See more:

Hi All,

As per my requirement in my complete system it consists of both desktop and web application. Desktop application(OCASIONALLY CONNECTED APPLICATION) will be accessing the data from local database and will be in sync with central database hosted on server.

Desktop application(online\offline data access): windows xp/vista/win7, .Net framework 3.5, MySql.
Web application(online data access): PHP, MySql.
Server(central data source): windows server, MySql (DB).

So what approach can I opt to establish offline\online system. Considering there will be one million desktops using the local DB's synchronizing with central DB.

Thanks in advance,

Ashok

Posted 16-Feb-12 20:08pm

ashok_rgm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

krumia · Accepted Answer · 2012-02-16T21:23:00

I don't think you can bear the burden of comparing whole databases.

What you can do is..
1. implement a publisher-subscriber architecture.
2. main server adds messages to a message queue when a database change happens.
3. desktop applications subscribe to the main server and get messages from the message queue.
4. desktops modify their local database according to the messages
5. whenever desktops come online, they will only retrieve the messages which they haven't retrieved before.

And since you cannot make messages out of every change to the database, choose the best subset that should be synchronized.