Content deleted Content added
There was a Script warning on the page from a cite book template, "Category:CS1 maint: date and year", fixed by removing the redundant date= field as year= was already set |
Altered template type. Add: volume, series, isbn, pages, date, title, chapter, doi, chapter-url, authors 1-4. Removed or converted URL. Changed bare reference to CS1/2. Upgrade ISBN10 to 13. | Use this tool. Report bugs. | #UCB_Gadget |
||
Line 2:
{{redirect|Elastic computing|the physical property|Elasticity (physics)|the economics measurement|Elasticity (economics)}}
In [[computing]], '''elasticity''' is defined as "the degree to which a system is able to adapt to workload changes by provisioning and de-provisioning [[System resource|resources]] in an [[Autonomic computing|autonomic]] manner, such that at each point in time the available resources match the current demand as closely as possible".<ref>{{cite
In the world of [[distributed system|distributed systems]], there are several definitions according to the authors, some considering the concepts of [[scalability]] a sub-part of elasticity, others as being distinct.
Line 25:
===Elasticity requirements===
When deploying applications in cloud infrastructures (IaaS/PaaS), requirements of the stakeholder need to be considered in order to ensure proper elasticity behavior. Even though traditionally one would try to find the optimal trade-off between cost and quality or performance, for real world cloud users requirements regarding the behavior are more complex and target multiple dimensions of elasticity (e.g., SYBL<ref>
===Multiple levels of control===
Cloud applications can be of varying types and complexities, with multiple levels of artifacts deployed in layers. Controlling such structures must take into consideration a variety of issues, an approach in this sense being [http://www.infosys.tuwien.ac.at/research/viecom/SYBL rSYBL].<ref>
==See also==
|