RousselTMLEARNING

Article · Cloud Computing: From Discovery to Expertise

Elasticity vs scalability

1. Vertical vs horizontal scalability #

Understanding how to increase processing power.

Scale-up vs scale-out #

Vertical scalability (scale-up) means adding RAM or CPU to a server. It has physical limits. Horizontal scalability (scale-out) means adding new identical servers, offering virtually unlimited growth.

2. Elasticity: autoscaling in action #

Elasticity is a system's ability to automatically add or remove resources based on precise metrics (CPU > 70% or network latency). It is what lets you save money at night and handle the load during sales.

3. Designing for high availability #

To be elastic, an application must be 'stateless' (no local state). Sessions must be stored in external databases or caches (Redis) so that servers can appear and disappear without cutting users' connections.

Hands-on: scaling #

Scalability commands.

Diagram #

Elasticity, vertical and horizontal scalability
Elasticity is the ability to adjust scalability automatically.

Examples #

# Scalabilité horizontale manuelle (Kubernetes)
kubectl scale deployment web --replicas=6
# Élasticité : ajustement automatique selon le CPU
kubectl autoscale deployment web --cpu-percent=70 --min=2 --max=20

# AWS Auto Scaling : politique de suivi de cible
aws autoscaling put-scaling-policy --auto-scaling-group-name web-asg --policy-name cpu70 --policy-type TargetTrackingScaling \
  --target-tracking-configuration '{"PredefinedMetricSpecification":{"PredefinedMetricType":"ASGAverageCPUUtilization"},"TargetValue":70}'

📄 Elasticity vs scalability: the keys to performance →

My progress

  • ⏱ Estimated time : ≈ 5 min

Sign in to track your progress and take notes. Sign in

💬 Questions about this lesson

No questions yet: be the first to ask for help or share your configuration.

Ask a question about this lesson →

Recommended Articles

Compute on AWS: EC2, Auto Scaling, Lambda and containers

Choose and use AWS compute services: EC2 instances (types, AMIs, EBS, user data, purchasing model...

Google Cloud networking: global VPC, subnets, firewall and load balancing

Design networking on Google Cloud: global VPC and regional subnets, firewall rules based on tags ...

Azure networking: VNet, NSG, peering, load balancing and hybrid connectivity

Design networking on Azure: virtual networks and subnets, network security groups (NSG), peering ...

HAProxy in Kubernetes: the high-performance Ingress Controller

Discover in depth how HAProxy integrates with Kubernetes: direct-to-pod architecture, hot update ...

What is cloud computing? The NIST definition

Understand the fundamentals of cloud computing through the 5 essential characteristics defined by...

Cloud native: definition and principles of a cloud native application

What is cloud native? The CNCF definition, the principles of a cloud native application (microser...

Cloud deployment models: public, private, hybrid, community and multi-cloud

Understand cloud computing deployment models according to NIST: public, private, community and hy...

Cloud best practices: security, resilience, costs and operations

Cloud computing best practices: pillars of a well-architected design, IAM and least privilege, mu...

IaaS, PaaS, SaaS: differences and examples of cloud service models

IaaS, PaaS, SaaS: what is the difference? Definitions, concrete examples (AWS, Azure, Google Clou...

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!