dido:public:ra:1.4_req:2_nonfunc:08_elasticity
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:08_elasticity [2021/06/04 15:21] char ToDo checked: Please Review |
dido:public:ra:1.4_req:2_nonfunc:08_elasticity [2021/07/26 12:40] (current) murphy [About] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 4.3.9 Elasticity ====== | ====== 4.3.9 Elasticity ====== | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] | ||
| - | * **<color #FF0000><todo @char #char:2021-06-04>Please Review</todo></color>** | + | [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] |
| ===== About ===== | ===== About ===== | ||
| Line 20: | Line 19: | ||
| The following are the various strategies used to achieve elasticity: | The following are the various strategies used to achieve elasticity: | ||
| * **Cost-aware criteria**: The default is to assume that there is a firm fixed price for IaaS providers, however, some providers allow for spot pricing schemes (i.e., Amazon) which can allow users to tap into IaaS excess capacity. This excess capacity is there so that the IaaS provider can meet the Service Level Agreements (SLAs) guaranteed to all customers. | * **Cost-aware criteria**: The default is to assume that there is a firm fixed price for IaaS providers, however, some providers allow for spot pricing schemes (i.e., Amazon) which can allow users to tap into IaaS excess capacity. This excess capacity is there so that the IaaS provider can meet the Service Level Agreements (SLAs) guaranteed to all customers. | ||
| - | * **Power-aware cost function**: Using the power required to meet the application's needs and little more, i.e., using off-peak power consumption only. | + | * **Power-aware cost function**: Using the power required to meet the [[dido:public:ra:xapend:xapend.a_glossary:a:application|application's]] needs and little more, i.e., using off-peak power consumption only. |
| * **Multiple classes of requests**: Allow applications to be segmented into categories based on the need for service. For example, customers' requests for service from the application can be divided into three categories: High Priority for performing financial transactions; Medium Priority for those making product inquiries; Low priority for simple browsing. | * **Multiple classes of requests**: Allow applications to be segmented into categories based on the need for service. For example, customers' requests for service from the application can be divided into three categories: High Priority for performing financial transactions; Medium Priority for those making product inquiries; Low priority for simple browsing. | ||
| * **Scaling multiple applications**: Allow an application to be broken up into smaller applications whose functionality and services are orchestrated. | * **Scaling multiple applications**: Allow an application to be broken up into smaller applications whose functionality and services are orchestrated. | ||
| Line 27: | Line 26: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:08_elasticity| Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:08_elasticity| Return to Top]] | ||
| - | //<color #FF0000><todo>TBD - to be added/expanded in future revisions of the DIDO RA</todo></color>// | + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> |
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.4_req/2_nonfunc/08_elasticity.1622834519.txt.gz · Last modified: 2021/06/04 15:21 by char
