Farms are isolated units, so if those 30 applications don't have any interdependencies, they should each be represented as a Farm (with a single Role in them, and a single Instance of that Role).
Does that help? If you can elaborate on your concern, we can give you more guidance. On Fri, Aug 14, 2015 at 2:59 PM Dmitri Toubelis <[email protected]> wrote: > I work for a client who is currently using RightScale for orchestration > but they want to get off because of the cost. They asked me to look into > Scalr and see if it would be a good fit. The client has ~50 instances > running in the amazon and 30 of them are single tier/single server > applications. I'm trying to wrap my head around how to fit them into Scalr. > Should it be one farm/one role per server or is there a better way? It > seems to me so far that Scalr (as name suggests :-) is good for scaling > architectures but I'm not sure if it is a good fit for non-scalable single > tires deployments. Are there any best practices for this use case? Any help > is appreciated. Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
