[WebDNA] two ideas for running a cluster of WebDNA servers
This WebDNA talk-list message is from 2019
It keeps the original formatting.
numero = 114878
interpreted = N
texte = 2506 1.- one front-end server that will redirect the requests 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 slave = 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 = servers, 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, so, 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@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
2506 1.- one front-end server that will redirect the requests 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 slave = 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 = servers, 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, so, 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@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
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...
Related Readings:
Alcatraz must have been nicer than this... (2000)
problems with 2 tags (1997)
[WebDNA] WebDNA Crashing or Not (2008)
Showif, Hideif reverse logic ? (1997)
creating a ShipCosts database (1997)
Multiple Pulldowns (1997)
Problems with cybercash (2000)
Unique SKUs (2000)
Possible Bug in 2.0b15.acgi (1997)
Help with database strategy (1998)
Form based Redirect (2001)
followup to ws3 vs ws2.1 speed (1998)
RE: IIS4b2 and WebCatalog b19 (1997)
WebCat editing, SiteGuard & SiteEdit (1997)
I got caught! (2003)
syntax question, not in online refernce (1997)
Shownext! (1998)
Problems with date math (1997)
frames & carts (1997)
Erotic Sites (1997)