concept elasticity in category reactive

appears as: elasticity
Reactive Application Development

This is an excerpt from Manning's book Reactive Application Development.

Elastic architectures are key for distributed computing. They’re expected to expand and contract as load demands change through elasticity—the ability to add or remove nodes on the fly. This unique feature allows these architectures to scale in and out and up and down, without the need for the application to be redesigned or rewritten. Elasticity also mitigates risk in that hardware can be used on demand, which eliminates the need to keep a bank of unused servers waiting for a load spike to occur. The technique that allows for this elastic behavior is location transparency, which uses logical names to find network resources, removing the need to know the physical locations of the users and the resource. We cover elasticity in detail in chapters 2 and 3, which explore the Akka actor model.

4.4. Increasing elasticity

We’ve spent a great deal of time laying out the analogy and establishing the overall system in a reactive format. As a result, you have the groundwork to explore more complex concepts (such as elasticity) in detail. As you may recall from chapter 1, elasticity means that the system stays responsive under varying workloads. Reactive systems can respond to changes in load by increasing or decreasing the allocation of resources.