question

prrincerathod-9761 avatar image
0 Votes"
prrincerathod-9761 asked ArnabPatra-8381 commented

Difference between scalability and elasticity

What is the difference between Scalability and Elasticity

azure-cloud-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PranathiPanyam-MSFT avatar image
1 Vote"
PranathiPanyam-MSFT answered ArnabPatra-8381 commented

@prrincerathod-9761 Welcome to Microsoft Platform. Thank you for posting your query here.

Scalable environments only care about increasing capacity to accommodate an increasing workload.
Elastic environments care about being able to meet current demands without under/over provisioning, in an autonomic fashion.

The key difference is, scalable systems don't necessarily mean they will scale up/down - it's only about being able to reach peak loads. Elastic workloads, however, will recognize dynamic demands and adapt to them, even if that means reducing capacity.

An example being, you have a web app that needs to support 1,000 active users for one day, so you meet that demand by provisioning 10 servers in total - but after that one day, you only ever have 10 active users, thus you only need 1 server. In this case, a scalable system would be able to scale to meet the 1,000 active users with the additional 9 servers - so that's cool, our system scaled! But now we're left with an abundance of over-provisioned capacity and we have to deal with that.

If our system was elastic for the above example, the process would have been automatic - our environment would have recognized the increasing workload, so it would have provisioned the necessary resources. Then when that day was over and the workload decreased significantly, our systems would have de-provisioned the servers as we didn't need them anymore.

Hope this helps!

Kindly let us know if the above helps or you need further assistance on this issue.



Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

As per microsoft doc (link:overview) "Services covered by Azure Autoscale can scale automatically to match demand to accommodate workload. They will scale out to ensure capacity during workload peaks and scaling will return to normal automatically when the peak drops."

which indicating scalability can reduce to normal after serve te pick load.

in the same page microsoft also mentioned "Horizontal scale is elastic: You can add more instances if load increases, or remove them during quieter periods."


these are denying your explanation.Would wait to hear more from u.



0 Votes 0 ·
PranathiPanyam-MSFT avatar image
0 Votes"
PranathiPanyam-MSFT answered

@prrincerathod-9761 Just checking in to see if the above answer helped. If this answers your query, do click “Mark as Answer” and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further queries do let us know.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.