Beyond POLB (Plain Old Load Balancing)
•Descargar como PPTX, PDF•
0 recomendaciones•644 vistas
A lot of things have changed since the 1990s, when POLB was born. It's time to go beyond POLB, beyond algorithms and into architectures.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Beyond POLB (Plain Old Load Balancing)
Similar a Beyond POLB (Plain Old Load Balancing) (20)
Más de Lori MacVittie
Más de Lori MacVittie (14)
Último
Último (20)
Beyond POLB (Plain Old Load Balancing)
- 1. Beyond POLB (Plain Old Load Balancing)
- 2. Scalability is how we maintain performance and availability
- 3. UP OUT How do we usually scale today?
- 4. POLB (Plain Old Load Balancing) How do we scale OUT today?
- 5. POLB (Plain Old Load Balancing) • Born in the mid 1990s • Distributes load based on network variables • Focused on algorithms, not architecture Traffic goes in Traffic goes out
- 6. But architectures and apps are changing THEN MONOLITHIC MICROSERVICES & APIs NOW
- 7. And so are “users” THEN Humans NOW Humans, Systems, Things
- 8. L7 LB Layer 7 Load Balancing Modern apps need modern scalability
- 9. and more …
- 10. L7 LB SECURITY OPTIMIZATION It’s time to go beyond POLB MANO
- 11. L7 Proxy (Layer 7 Proxy) GOAL: EFFICIENCY & AGILITY
- 12. L7 Proxy (Layer 7 Proxy) GOAL: EFFICIENCY & AGILITY • Data Partitioning (Sharding) Architectures • Complex URL dispatch • Manipulate response headers • Dynamic routing based on backend data • Scaling by Functional Decomposition
- 13. L7 Proxy (Layer 7 Proxy) GOAL: SECURITY
- 14. L7 Proxy (Layer 7 Proxy) GOAL: SECURITY • Layer 7 (App) DDoS Protection • Web appl firewalling • OWASP Top 10 • App access control • Federated identity
- 15. L7 Proxy (Layer 7 Proxy) GOAL: PERFORMANCE
- 16. L7 Proxy (Layer 7 Proxy) GOAL: PERFORMANCE • TCP Multiplexing • Caching • Performance-based load distribution • Auto-scalability • Minification • HTTP Compression • Buffering • Script aggregation • SSL Offload
- 17. L7 Proxy (Layer 7 Proxy) GOAL: MANO (Management and Orchestration)
- 18. L7 Proxy (Layer 7 Proxy) • REST and SOAP APIs • Plug-ins for Chef, Puppet, Cisco, VMware, Electric Cloud, New Relic, Nagios, Ansible, Urban {code}, and more • Smart templates GOAL: MANO (Management and Orchestration)
- 19. Caching Minification App Security App Access DDoS Protection Multiplexing POLB L7 LB Auto-Scaling GO BEYOND POLB MANO GO
Notas del editor
- Performance and availability. Business. Engagement. If we don’t scale, the business doesn’t grow, we impede productivity. We lose.
- How do we scale (everything) today? Up or out.
- How do we scale out? This is the monolithic approach. Who cares as long as it scales? Each of these servers Must be a complete system Must be able to answer every API call Which results in A huge footprint Stands opposed to microservices principles And doesn’t support Functional partitioning for scale Version management Modern concepts like purpose-driven routing
- We need the ability to route, direct, and distribute load based on modern architectures that include highly decomposed applications (microservices), multiple versions of the same app and APIs and an increasingly diverse set of devices and things accessing those applications. That’s why we need L7 LB – because it has the visibility necessary and the strategic location in an architecture (up front) to make the kinds of decisions required to support modern, scalable architectures.
- How do you scale using L7 LB? We look to the Scale Cube to see how we can achieve this.