Discover secrets of containers scalability and learn how to automate the process of resource allocation, load balancing and traffic distribution across multiple containers within one clustered environment.
7. Issues that prevent us to do scaling
• Application is not designed for scaling
• We cannot predict our spikes
• The provisioning of each new instance takes much time
• We never know what bottlenecks to expect
13. Static website Web frontendUser DB Queue Analytics DB
Development
VM
QA server Public Cloud Contributor’s
laptop
MultiplicityofStacks
Production
Cluster
Customer Data
Center
…that can be manipulated
using standard operations
and run consistently on
virtually any hardware
platform
An engine that enables any
payload to be encapsulated
as a lightweight, portable,
self-sufficient container…
Docker is a shipping container system for code
Multiplicityofhardware
environments
Doservicesandapps
interactappropriately?
CanImigratesmoothly
andquickly?
19. • You must use load balancer once
you scale an app horizontally
• Keep look at sticky load balancing
• Load balancer can be scaled
horizontally
• Dynamic scaling in and out is also
possible!
Load balancing consideration
20. Scaling of the web layer
• Should be done just in time
• Load balancer should be aware
of resizing at the web layer
• Requires additional actions for
stateful applications:
• Use of storage replication
• Use of shared persistent
storage
21. Database scaling consideration
• Relational databases usually
scale good only vertically
• Relational database usually can’t
be scaled horizontally in a
runtime
• We have to prepare a database
cluster of a fixed size