I advise running both apps on the same server and allow the load balncer to distribute the load.
Why do you need two discrete roles? If the answer is because that's how it used to be done with our own hardware it's time to challenge those practices. If the two apps do enough work to warrant two app roles scalr will spawn another. It may be though you could use a single medium instance to host both and still have plenty of headroom. In our tests with our apps a single med instance outperforms 3 small instances saving us .10/hr. Per med instance. And we now run 3 rails apps and one Sinatra app on our app role. On Jul 8, 2009, at 11:42 PM, Frédéric Sidler <[email protected]> wrote: > > There is a 4th role you should consider for this purpose. This is not > www, app or mysql role. > > On Thursday, July 9, 2009, kenvogt <[email protected]> wrote: >> >> I need a farm with a database server, a web server, and two distinct >> application servers for backend processing. When I login to Scalr and >> go to build a new farm, select Shared Roles, then Application >> servers, >> it only allows me to check a box for a server type. I need two of the >> app64 however. This is not a scaling issue, the servers need to do >> different things. How can I do this? >> >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
