This shows you the differences between two versions of the page.
|
dido:public:ra:xapend:xapend.a_glossary:v:verticalscaling [2020/11/16 21:22] nick created |
dido:public:ra:xapend:xapend.a_glossary:v:verticalscaling [2021/10/04 13:40] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Vertical Scaling ===== | ===== Vertical Scaling ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary | Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| **Vertical Scaling** refers to adding more [[dido:public:ra:xapend:xapend.a_glossary:c:cpu|CPU]], memory, or I/O resources to an existing [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]], or replacing one server with a more powerful server. Amazon Web Services (AWS) vertical scaling and Microsoft Azure vertical scaling can be accomplished by changing [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]] sizes, or in a data center by purchasing a new, more powerful appliance and discarding the old one. AWS and Azure cloud services have many different instance sizes, so scaling vertically is possible for everything from EC2 instances to RDS databases. | **Vertical Scaling** refers to adding more [[dido:public:ra:xapend:xapend.a_glossary:c:cpu|CPU]], memory, or I/O resources to an existing [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]], or replacing one server with a more powerful server. Amazon Web Services (AWS) vertical scaling and Microsoft Azure vertical scaling can be accomplished by changing [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]] sizes, or in a data center by purchasing a new, more powerful appliance and discarding the old one. AWS and Azure cloud services have many different instance sizes, so scaling vertically is possible for everything from EC2 instances to RDS databases. | ||