Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
GLUE CON 2015
Architectural Patterns for Scaling Microservices
and APIs
Scalability is not a Singleton
You have
less than 5
seconds to
deliver
content.
Maintain availability
Maintain performance...
Scale is achieved by optimally distributing
load
 TCP Connections
 Response time
 HTTP Requests
 Least connections
 F...
The Scale Cube
 X-axis
 Y-axis
 Z-axis
http://microservices.io/articles/scalecube.html
Scalability: Out, Up, and Across
 Creating scalability
domains
 Balance
performance and
availability
X-Axis
 Like clustering
 Leverages cloning
 Typically operates at layer
4 (TCP)
Y-Axis
 Like routing
 Uses identifiable variables
(usually from HTTP headers)
 Operates at layer 7 (HTTP)
Z-Axis
 Like sharding
 Uses one or more identifiable variables (usually from HTTP headers)
 Operates at layer 7 (HTTP)
APIs and Microservices
API as Façade API as Endpoint
SERVICE
API
API
SERVICE
API
SERVIC
E
A
P
I
SERVIC
E
A
P
I
API as Endpoint
API
Standard X-axis Scaling Pattern
APIAPI
API Façade: Interpolated in Network
Standard Y-axis Scaling Pattern
Microservice A
Microservice B
Microservice C
API
One pattern is rarely enough
Most often combined in 2-3 tiers
 Y-axis routing pattern used to
distribute API calls to X-axis
scaled service clusters
2-Tier Interpolated API
Y-Axis Scaling X-Axis Scaling
API
Top Mistakes Regardless of
Pattern
• Choosing the wrong thresholds
• Scaling too late leads to time outs &
performance deg...
@lmacvittie
F5 Networks
THANK YOU!
Nächste SlideShare
Wird geladen in …5
×

Architectural Patterns for Scaling Microservices and APIs - GlueCon 2015

3.792 Aufrufe

Veröffentlicht am

Presentation on scaling patterns for microservices and APIs.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

Architectural Patterns for Scaling Microservices and APIs - GlueCon 2015

  1. 1. GLUE CON 2015 Architectural Patterns for Scaling Microservices and APIs
  2. 2. Scalability is not a Singleton You have less than 5 seconds to deliver content. Maintain availability Maintain performance Average cost of critical app failure per hour is $500,000 to $1 million.
  3. 3. Scale is achieved by optimally distributing load  TCP Connections  Response time  HTTP Requests  Least connections  Fastest response  Fastest app  Round Robin Thresholds Methods
  4. 4. The Scale Cube  X-axis  Y-axis  Z-axis http://microservices.io/articles/scalecube.html
  5. 5. Scalability: Out, Up, and Across  Creating scalability domains  Balance performance and availability
  6. 6. X-Axis  Like clustering  Leverages cloning  Typically operates at layer 4 (TCP)
  7. 7. Y-Axis  Like routing  Uses identifiable variables (usually from HTTP headers)  Operates at layer 7 (HTTP)
  8. 8. Z-Axis  Like sharding  Uses one or more identifiable variables (usually from HTTP headers)  Operates at layer 7 (HTTP)
  9. 9. APIs and Microservices API as Façade API as Endpoint SERVICE API API SERVICE API SERVIC E A P I SERVIC E A P I
  10. 10. API as Endpoint API Standard X-axis Scaling Pattern APIAPI
  11. 11. API Façade: Interpolated in Network Standard Y-axis Scaling Pattern Microservice A Microservice B Microservice C API
  12. 12. One pattern is rarely enough
  13. 13. Most often combined in 2-3 tiers  Y-axis routing pattern used to distribute API calls to X-axis scaled service clusters
  14. 14. 2-Tier Interpolated API Y-Axis Scaling X-Axis Scaling API
  15. 15. Top Mistakes Regardless of Pattern • Choosing the wrong thresholds • Scaling too late leads to time outs & performance degradation • Not monitoring • Services fail, users get angrified by time outs • Not scaling the scaler • Overwhelming the upstream scaler is a Very Bad Thing™
  16. 16. @lmacvittie F5 Networks THANK YOU!

×