your php app will need to be configured to access the mysql db. Your php app you're probably has a configuration file with a string such as 'username:passw...@localhost/db_name' (just an example) where username and password are those of the mysql server. When you move the db to a separate server, you need to change 'localhost' to the internal hostname of the mysql server, which will be something like int- mysql...@mydomain.
Further, as you scale, your php app must be configured to write to the mysql master and read from the slave(s). Consult your php app documentation for details. On Mar 25, 2009, at 2:17 PM, domhol wrote: > > Hi Guys, > > > Sorry for being really simple here, but just trying to get my head > around this. > > If I have an php app on the app server which uses a mysqld database, > if i setup a mysql server seperately, when the app needs to read/write > from the sql database how does the application know to use the sql > server to access the sql database? > > Also, if my app servers and databse servers scale according to demand, > how do the scaled database servers write to the mysql database, when > only one instance can write to the mysql database at a time. As from > my understanding only the master can write from the database, and all > scaled database servers will access a snapshot which is read-one... > Really confused about all this?? > > Some light shed would be fantastic.. Also, if anyone has used wowza > on scalr and how the app would access a wowza server also would be > great to know. > > Cheers, > > Dominic > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
