1.- one front-end server that will redirect the reque=sts through POST or GET to a cluster of back-end servers. When the request =is for writing, then only one of the back-end servers is solicited (always =the same), when is is for reading, it could be any of the back-end servers.=
The "writing" server is the master, the others are slaves. Every =30 sec, through rsync, the master is copied to a slave, and the WebDNA slav=e reloads the databases in RAM. Meanwhile, the front-end server will direct= the reading requests to the other back-end servers, and this sequentially.=
Another idea would be the same front-end server with the same backend serve=rs, and instead of using rsync, the front end server would POST the request= to each one of the back-end servers: no more master and slave.
Another idea would be to keep a log database of all the writing requests, s=o, by reading this log file, all the "slaves" would get the same =information. Databases could even be rebuilt in case of necessity.
I am sure there are other solutions. Any other idea?
- chris
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@w=ebdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: suppo=rt@webdna.us
1.- one front-end server that will redirect the reque=sts through POST or GET to a cluster of back-end servers. When the request =is for writing, then only one of the back-end servers is solicited (always =the same), when is is for reading, it could be any of the back-end servers.=
The "writing" server is the master, the others are slaves. Every =30 sec, through rsync, the master is copied to a slave, and the WebDNA slav=e reloads the databases in RAM. Meanwhile, the front-end server will direct= the reading requests to the other back-end servers, and this sequentially.=
Another idea would be the same front-end server with the same backend serve=rs, and instead of using rsync, the front end server would POST the request= to each one of the back-end servers: no more master and slave.
Another idea would be to keep a log database of all the writing requests, s=o, by reading this log file, all the "slaves" would get the same =information. Databases could even be rebuilt in case of necessity.
I am sure there are other solutions. Any other idea?
- chris
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@w=ebdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: suppo=rt@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...