Understanding the core components and their use will help you get the most out of Scalr.
| Farms | Logical units that contain a set of roles. Roles are configured within farms (auto-scaling, deployments etc.) |
|---|---|
| Roles | Machine images with a specific behavior (e.g application server, database, caching server etc.) |
| Servers | Instances of a specific role. |
| Scaling | Provisioning of additional instances of a given role. Can be automated to follow the evolution of various metrics and closely follow the demand curve for your application by adding new servers when you need them and shedding unneeded instances. This is auto-scaling. |
| Deployments | A feature that allows you to orchestrate code deployment to your farms. By linking to a source you can tie your application to a farm role. |
| Orchestration Engine | A powerful tool for event-based, manual, or even recurring (with the Task Scheduler) script execution. |
| Chef | An open-source systems integration framework built specifically for automating the cloud. With Chef, you write abstract definitions as source code to describe how you want each part of your infrastructure to be built and apply these to your servers |
| Domain Name Management | Out-of-the-box DNS management tool. DNS zones are automatically updated by Scalr to reflect the instances you are currently running. |
| Clouds supported | Infrastructure as a service provided by Cloud providers such as Amazon Web Services. A cloud can be public or private. Scalr works on top of cloud APIs. |

Labels
Page: Farms
Page: Roles
Page: Servers and Instances
Page: Scaling
Page: Deployments
Page: Domain Name Management
Page: Orchestration Engine
Page: Chef
Page: Monitoring
Page: Service Configuration presets
Page: Architecture
Page: Storage
Page: Failover
Page: Parameters