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
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)
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.