Re: [WebDNA] two ideas for running a cluster of WebDNA servers
This WebDNA talk-list message is from 2019
It keeps the original formatting.
numero = 114881
interpreted = N
texte = 2509 Number 2 please. I did something similar when we hosted the LA Rams site bac= k in 2000 for the nfl championships and Super Bowl.=20 > On Oct 5, 2019, at 07:41, christophe.billiottet@webdna.us wrote: >=20 > =EF=BB=BF1.- one front-end server that will redirect the requests through P= OST 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. >=20 > The "writing" server is the master, the others are slaves. Every 30 sec, t= hrough rsync, the master is copied to a slave, and the WebDNA slave reloads t= he databases in RAM. Meanwhile, the front-end server will direct the reading= requests to the other back-end servers, and this sequentially. >=20 > Another idea would be the same front-end server with the same backend serv= ers, 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. >=20 > 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. >=20 > I am sure there are other solutions. Any other idea? >=20 >=20 > - chris >=20 >=20 >=20 >=20 > --------------------------------------------------------- > 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 --------------------------------------------------------- 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:
2509 Number 2 please. I did something similar when we hosted the LA Rams site bac= k in 2000 for the nfl championships and Super Bowl.=20 > On Oct 5, 2019, at 07:41, christophe.billiottet@webdna.us wrote: >=20 > =EF=BB=BF1.- one front-end server that will redirect the requests through P= OST 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. >=20 > The "writing" server is the master, the others are slaves. Every 30 sec, t= hrough rsync, the master is copied to a slave, and the WebDNA slave reloads t= he databases in RAM. Meanwhile, the front-end server will direct the reading= requests to the other back-end servers, and this sequentially. >=20 > Another idea would be the same front-end server with the same backend serv= ers, 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. >=20 > 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. >=20 > I am sure there are other solutions. Any other idea? >=20 >=20 > - chris >=20 >=20 >=20 >=20 > --------------------------------------------------------- > 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 --------------------------------------------------------- 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 .
Bob Minor
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:
Websited Development (1999)
Sorting problem (2002)
Multiple catalog databases and showcart (1997)
Improved ISAPI extension (2004)
Possible Bug in 2.0b15.acgi (1997)
Weird Problem (1997)
[WebDNA] Webdna and CMS (2012)
How does the Globals folder work? (2000)
database size? (1997)
shipcost (1997)
ARGH! (2004)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
Re:E-Mailer (WebCatb15acgiMac) (1997)
Re:WebCatalog f2 Installation (1997)
Bug in 4.5 - Needs to be fixed ASAP. (2002)
Content search & results (2008)
Navigator 4.01 (1997)
Time formatting in linux (2006)
Using Plug-In while running 1.6.1 (1997)
Rhapsody? (1997)