b. Understand scaling concepts for a Cloud application and steps to scale an application in IBM Bluemix PaaS
1. Vertical scaling by increasing resources to an application instance
Vertical scaling increases the resources available to an application by adding capacity directly to the individual nodes — for example, adding additional memory or increasing the number of CPU cores.
2. Horizontal scaling by increasing the number of application instance
Horizontal scaling is often referred to as scaling out. The overall application resource capacity grows through the addition of entire nodes. Each additional node adds equivalent capacity, such as the same amount of memory and the same CPU. Horizontal scaling typically is achievable without downtime.
3. Understand how to manually scale applications through IBM Bluemix PaaS dashboard
The IBM Bluemix PaaS UI Dashboard supports both vertical and horizontal scaling through increasing the amount of memory and increasing the number of instances of an application runtime. Both techniques can be applied to the same application:
4. Automatically scaling applications in IBM Bluemix PaaS using the Auto-Scaling service and scaling policy fields and options such as: available metric types for runtimes, breach duration, and cooldown period.
The Auto-Scaling service has control panels to define scaling policy, view metrics, and view scaling history. A scaling policy is based on thresholds for various metrics such as Memory, JVM Heap, Throughput, and Response time. The breach duration in the policy defines how long a threshold may be exceeded before a scaling event is performed. The cooldown period in the policy is how long to wait after a scaling event before monitoring for exceeded thresholds.
Reference: https://www.ng.bluemix.net/docs/#services/Auto-Scaling/index.html#autoscaling
1. Vertical scaling by increasing resources to an application instance
Vertical scaling increases the resources available to an application by adding capacity directly to the individual nodes — for example, adding additional memory or increasing the number of CPU cores.
2. Horizontal scaling by increasing the number of application instance
Horizontal scaling is often referred to as scaling out. The overall application resource capacity grows through the addition of entire nodes. Each additional node adds equivalent capacity, such as the same amount of memory and the same CPU. Horizontal scaling typically is achievable without downtime.
3. Understand how to manually scale applications through IBM Bluemix PaaS dashboard
The IBM Bluemix PaaS UI Dashboard supports both vertical and horizontal scaling through increasing the amount of memory and increasing the number of instances of an application runtime. Both techniques can be applied to the same application:
The Auto-Scaling service has control panels to define scaling policy, view metrics, and view scaling history. A scaling policy is based on thresholds for various metrics such as Memory, JVM Heap, Throughput, and Response time. The breach duration in the policy defines how long a threshold may be exceeded before a scaling event is performed. The cooldown period in the policy is how long to wait after a scaling event before monitoring for exceeded thresholds.
Reference: https://www.ng.bluemix.net/docs/#services/Auto-Scaling/index.html#autoscaling
0 comments:
Post a Comment