OK sounds good. So, I imagine one will have to port the data over to the new server. It just seems like there might be some loss of data if the time takes too long between swithcing. i guess we cross the bridge when it comes.
On Aug 26, 5:23 pm, John Yerhot <[email protected]> wrote: > I wouldn't worry about scaling till you have to do it. > > But, going from a 1 server setup (app and db on the same server) to a > 2 server setup (1 app and 1 db) is pretty easy. All you'd have to > really do to your app is change your database.yml to point to your new > db server. > > On Aug 26, 2:04 pm, "tashfeen.ekram" <[email protected]> wrote: > > > > > I am getting ready deploy my app and trying to figure its > > configuration to allow for scaling if needed. I am looking at > > deploying on Amazon. I do not expect high traffic in the beginning > > (though that is completely a conjecture), i was thinking of deploying > > the whole app including a MySQL on the single instance. I am trying to > > figure out how difficult would it be if I had to separate the > > components with having the db on its own instance with balance loading > > and front end servers all running on their own instances. Is it easy > > to make that transition or is it difficult enough that one should just > > setup the more redundant setup now to avoid the difficulty. > > > thanks!- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
