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 = 114884
interpreted = N
texte = 2512 > Nice idea Chris, however 30 seconds to replicate is far too slow in an = ecommerce or high usage client data entry site. the idea is to exclude the server being written on from the round robin = cluster during the 30 seconds it takes to rsync the databases with the = master. The experience would be transparent for the users. > The read from the slaves is OK but would mean another level of = infrastructure to balance the load across the slave servers, so in = effect a load balancer. WebDNA front-end can do this sequentially; it is easy to write a small = script that would send users to server 1, then to server 2, then to = server 3 etc=E2=80=A6 so the front end could operate as a load balancer. = It could even use a specific script to check if each server is up before = pointing users at it. > I know that the MySQL has been dropped from WebDNA yes, and I would like to explain why: MySQL belongs to Oracle, and the = licenses do not allow to embed the MySQL connectors inside WebDNA. Since = each flavor of linux has a different way of implementing these = connectors, (version/location) then we had to build as many WebDNA linux = versions as linux flavors, each case needed to be addressed. It means 10 = to 14 executables for WebDNA. 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:

    
  1. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Donovan Brooke 2019)
  2. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (christophe.billiottet@webdna.us 2019)
  3. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Brian Harrington 2019)
  4. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Donovan Brooke 2019)
  5. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (WebDNA Solutions 2019)
  6. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (WebDNA Solutions 2019)
  7. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Stuart Tremain 2019)
  8. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Stuart Tremain 2019)
  9. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (christophe.billiottet@webdna.us 2019)
  10. RE: [WebDNA] two ideas for running a cluster of WebDNA servers ("Scott @ Itsula" 2019)
  11. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Stuart Tremain 2019)
  12. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Bob Minor 2019)
  13. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (Greg Nelson 2019)
  14. Re: [WebDNA] two ideas for running a cluster of WebDNA servers (WebDNA Solutions 2019)
  15. [WebDNA] two ideas for running a cluster of WebDNA servers (christophe.billiottet@webdna.us 2019)
2512 > Nice idea Chris, however 30 seconds to replicate is far too slow in an = ecommerce or high usage client data entry site. the idea is to exclude the server being written on from the round robin = cluster during the 30 seconds it takes to rsync the databases with the = master. The experience would be transparent for the users. > The read from the slaves is OK but would mean another level of = infrastructure to balance the load across the slave servers, so in = effect a load balancer. WebDNA front-end can do this sequentially; it is easy to write a small = script that would send users to server 1, then to server 2, then to = server 3 etc=E2=80=A6 so the front end could operate as a load balancer. = It could even use a specific script to check if each server is up before = pointing users at it. > I know that the MySQL has been dropped from WebDNA yes, and I would like to explain why: MySQL belongs to Oracle, and the = licenses do not allow to embed the MySQL connectors inside WebDNA. Since = each flavor of linux has a different way of implementing these = connectors, (version/location) then we had to build as many WebDNA linux = versions as linux flavors, each case needed to be addressed. It means 10 = to 14 executables for WebDNA. 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:

Nav. 4 probs with cart - Serious problem (1997) [redirect] question (2005) mac hack (1997) can webcat create directories on NT? (1997) access denied problem (1997) select multiple 2 more cents (1997) Generating unique SKU from [cart] - Still Stumped... (1997) Grep Question - MAY NEVER BE SOLVED (2003) [WebDNA] Cheap tiny VPS running WebDNA 7.0 FastCGI !!! (2010) [append] and SSL (1997) Capacity question (2002) What's New Date (2002) Nesting format tags (1997) access denied problem (1997) Repeating Fields (1997) Counting LineItems (2000) [addfields] bombing 5.0 (2003) View order not right (1997) process SSI (1998) Serving images from databases (1998)