Scalability out and back

From OIAr Archive 2013
Revision as of 00:22, 12 November 2012 by Jan Schoonderbeek (talk | contribs) (start)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Informational
Informational
Page maturity
This page has maturity level 2 (young)


Document icon Scalability level out and back Version: 0.1 OIAr logo
Document type: QAdefinition Owner:

J.A.H. Schoonderbeek



Adaptability out and back has ordinal number 25. It's one-sentence description is:
"Capacity can be scaled out, but also back".

When a facility has both inward and outward scalability, then the capacity of the facility can be increased by deploying multiple instances of the facility itself, but also by removing previously added instances. For example:

  • a network connection can be scaled out by combining multiple connections in a single Etherchannel, and back by removing connections from the Etherchannel
  • an application platform farm of virtualized application servers can be scaled out by provisioning more virtual servers, and scaled back by decommissioning servers.