RE: [PHP] operational musings

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:jon@xxxxxxxxxxxxxxxxxx]
Sent: Tuesday, February 27, 2007 8:38 PM
To: Jay Blanchard
Cc: php-general@xxxxxxxxxxxxx
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


.

Relevant Pages

  • Re: installing DBD-Informix on fedora 6
    ... usually i authenticate on the db server by adding a line to the .rhosts file belonging to root. ... my "stores" database is empty, i use it only for testing connections. ... ESQLTEST Program Running: ... Using IBM Informix CSDK Version 2.90, IBM Informix-ESQL Version 2.90.UC2 from /opt/informix ...
    (perl.dbi.users)
  • Re: Info Store Help!!!
    ... I look after an SBS2003 client with 20 ... Hmmm - this is a message you saw on the server? ... I found the problem was the average disk queue length was at ... Offline Defrag against both the Public and Private stores. ...
    (microsoft.public.exchange.admin)
  • Bad Day (was: *Beats head off desk*)
    ... light is on, the USB hub is working, but the screen is kaput. ... I hit four stores - two consumer electronics, ... The server right away recognizes the new resolution, ... power button. ...
    (alt.games.warcraft)
  • Re: add stores to RSG
    ... lots of disk space for recovery using RSG so we don't have to consider extra ... add another server in the plan. ... separately for each storage group being restored. ... start recovering the information stores by replying transaction logs the ...
    (microsoft.public.exchange.admin)
  • Re: Information Store (DB) & Transaction logs growing to fast/ to quic
    ... One day our servers just went into overdrive and the stores ... Apparently this "Admin Assistant" only saw one public folder ... She called her friend who was on a different PF server ... size was that actually the IS itselft was growing out of proporsions too. ...
    (microsoft.public.exchange.misc)