>From my experience, database replication from the central server to each of the stores won't scale...
We use a timed (every X minutes), home-brewed protocol that does something similar to a synchronization. And, we don't synchronize the entire database at central server (as there are parts of the central server database that only apply to specific stores). And, there's *A LOT* of data at the central server... more than you want your local server databases dealing with if they're going to keep up with any strict performance expectations (ie. a real-time transaction processing system in an very busy retail location). > -----Original Message----- > From: Jon Anderson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 27, 2007 8:38 PM > To: Jay Blanchard > Cc: php-general@lists.php.net > Subject: Re: [PHP] operational musings > > Without any more than a few minutes worth of work, you can > make MySQL do > that with replication. Your in-store system could act as a > slave to for > the central system databases (any central updates trickle down to the > slave automatically) and your in-store machine could be the > master for > the store_xyz database(s). > > Network disconnect? No problem! > Network reconnect? Easy! > In-store machine failure? No problem! Just update the tables from the > central master! > Work? Almost none! > > And since this is a PHP list... > > <?= 'jon' ?> > > Jay Blanchard wrote: > > Howdy cats and kittens! > > > > I had an interesting thought after watching a demo of a POS > system and > > wondered if the same type of methodology could be applied in a PHP > > application. I haven't thought this all the way through, but a > > fully-hatched idea like this could signal a major change in > applications > > designed with PHP. > > > > In the POS if the network connectivity was lost the store > could continue > > to operate, once the network connectivity was restored the data from > > each store would sync back up and data would be sent to the central > > server, yadda, yadda, yadda. Of course this is in a client/server > > application with an executable residing on each workstation. > > > > So, if you wanted to do this with PHP you would likely have > to have a > > local web /database server (each store), establish a socket > (primary and > > store servers?) to watch for an outage/restore and then > write the code > > to support the sync up. Can it be done with PHP? It would > definitely be > > worth the trouble given the frequency that connections to stores get > > lost. > > > > Thanks in advance for ideas, thoughts, etc. > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
