Performance and Scalability with the Application Load Balancer Cloudlet

1. © AKAMAI - EDGE 2017
Performance and Scalability with the Application Load Balancer
Cloudlet
Divya Amin & Vishnu Atluri

2. © AKAMAI - EDGE 2017
 Challenges with current origin architectures
 What are Cloudlets
 Introduction to the Application Load Balancer Cloudlet
 Use-Case scenarios
 ALB vs other Akamai Products
 UI Demo
©2017 AKAMAI | FASTER FORWARDTM
Agenda

3. © AKAMAI - EDGE 2017
Overcoming latency
introduced when making
traffic load balancing
decisions at origin
Mitigating downtime risk
associated with
unreliable data center
infrastructure
Scaling infrastructure
capacity between data
centers during peak
demand
Providing a consistent and positive experience for global users
in the face of unpredictable application usage patterns and data
center health.
Challenge

4. © AKAMAI - EDGE 2017
More Apps are Moving to the Cloud through 2017-2018
Top business goals
driving cloud
investments
By 2018 the typical IT department with apps and
platforms residing in on-premisesystemswill
be the minority (40%).
Organizations are using multiple cloud models
to meet their business’s needs, including private (62%),
public (60%), and hybrid (26%).
Lowering total cost of ownership
Replacing legacy on-premise tech
Enabling business continuity
Source: IDG Enterprise Cloud Computing Survey, 2016.

5. © AKAMAI - EDGE 2017
ORIGIN DATACENTERS
Multi-region / multi-cloud origin architectures
Apps with high availability at the session level
on-premise
systems
private
cloud
public
cloud
hybrid
cloud
PERFORMANCE
RELIABILITY FLEXIBILITY CONTROLApplication Load Balancer Cloudlet

6. © AKAMAI - EDGE 2017
A Cloudlet is a value-added application that complements Akamai’s core delivery solutions to
solve specific business challenges.
Each Cloudlet lets you configure and control a Cloudlet’s behavior via a dedicated user interface
and an OPEN API.
What is a Cloudlet?

7. © AKAMAI - EDGE 2017
Available Cloudlets
Forward
Rewrite
Visitor
Prioritization
Edge
Redirector
API
Prioritization
Request
Control
Audience
Segmentation
Input
Validation
Phased
Release

8. © AKAMAI - EDGE 2017
Our Newest Cloudlet – Application Load Balancer
Forward
Rewrite
Visitor
Prioritization
Edge
Redirector
API
Prioritization
IP/Geo
Access
Audience
Segmentation
Input
Validation
Phased
Release
Application Load
Balancer

9. © AKAMAI - EDGE 2017
Cloudlets Club @ Developer Zone
We are available at the Developer Zone to discuss any queries about
our Cloudlets.

10. © AKAMAI - EDGE 2017
Application Load Balancer Cloudlet
Maximize application performance and availability with fast, flexible,
and reliable load balancing on Akamai’s Intelligent Platform

11. © AKAMAI - EDGE 2017
is a multi-layer load balancer leveraging attributes from both the application layer (Layer 7)
and the DNS layer (Layer 3) providing control over traffic directed to various data
sources.
Application Load Balancer
* SureRoute is only available for accelerated delivery ©2017 AKAMAI | FASTER FORWARDTM
Session Stickiness
Cookie Based Session Stickiness maintains control for consistent
session stickiness behaviors
Origin Health Checks
Origin Health Checks w/ Seamless Failover and Outage Response
No Hardware, No Code
Reduce complexity & offload routing logic from your data tier to
Akamai
Fast, Intelligent Routing
Akamai’s SureRoute algorithm provides high availability and instant
scale through dynamic route optimization and failover logic*
Easy to Setup
Easy to use interface, and included API, allow you to click to design
and activate policies and/or extend cloudlet controls to operations staff

12. © AKAMAI - EDGE 2017
 Prepare Netstorage (for hosting failover files)
 Create an empty ALB policy and save it
 Enable ALB in the delivery configuration and create Origin endpoint definitions
 Manage “Load Balancing Setup” to create load balancing strategies
 Update ALB policy to use appropriate load balancing setup
©2017 AKAMAI | FASTER FORWARDTM
Steps to get started

13. © AKAMAI - EDGE 2017
Common Use Case 1
Three private data-centers spread across the US. Running
active/active. Session stickiness very important as is failover.

14. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
HTTP Layer Based Rules:
• User location data
• URL path
• Ex. Micro services URL
routing
• Cookie
• Device characteristics
• Ex. Mobile users
• File Extensions
• Etc.
Simple Application Load Balancer
Setup -
one rule and one load balancing
setup
LTM  Local Traffic Manager
(ex. F5)

15. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Client makes a request
from New Jersey
1

16. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Client makes a request
from New Jersey
1
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2

17. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Serve
r 2
LTM
Data Center Chicago
Client makes a request
from New Jersey
1
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2
Rule A is associated with Load
Balancing Setup 1 which uses
performance load balancing to
send request to closest data
center
3

18. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Client makes a
request from San
Francisco
1

19. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Client makes a
request from San
Francisco
1
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2

20. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Client makes a
request from San
Francisco
1
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2
Rule A is associated with Load
Balancing Setup 1 which uses
performance load balancing to
send request to closest data
center
3

21. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
1 Client makes a
request from
Chicago

22. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2
1 Client makes a
request from
Chicago

23. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Serve
r 2
LTM
Data Center Chicago
Request matches to Rule A that
includes user location data based
on country with the client
connecting IP address
2
Rule A is associated with Load
Balancing Setup 1 which uses
performance load balancing to
send request to closest data
center
3
1 Client makes a
request from
Chicago

24. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Data Center in New Jersey
goes down: (e.g.
maintenance, outage, etc.)

25. © AKAMAI - EDGE 2017
Application Load Balancer
Load Balancing Use Case: Multiple DCs + Session Stickiness + Failover
Rule A
Load Balancing
Setup 1
Server
1
Server
2
LTM
Data Center New
Jersey
Server
1
Server
2
LTM
Data Center San Francisco
Server
1
Server
2
LTM
Data Center Chicago
Automatic Failover Occurs
sending New Jersey user to
Data Center in San
Francisco

26. © AKAMAI - EDGE 2017
Common Use Case 2
Hybrid setup with two private data centers and cloud instance.
Running non-critical assets in the cloud. Session stickiness important
as is failover.

27. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
HTTP Layer Based Rules:
• User location data
• URL path
• Ex. Micro services URL
routing
• Cookie
• Device characteristics
• Ex. Mobile users
• File Extensions
• Etc.

28. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
Client makes a request to
access their online banking
1
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4

29. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
1
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
That request gets
matched to Rule A
that includes session
stickiness
2
Client makes a request to
access their online banking

30. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
1
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
That request gets
matched to Rule A
that includes session
stickiness
2
Rule A is associated
with Load Balancing
Setup 1 which directs
traffic to either DC1 or
DC2
3
Client makes a request to
access their online banking

31. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
1 Client makes a request to view a
landing page or marketing website

32. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
1 Client makes a request to view a
landing page or marketing website
2 That request gets
matched to Rule B that
includes specific URL
Path

33. © AKAMAI - EDGE 2017
Load Balancing Use Case: Cloud Migration
Server
1
Server
2
LTM
Data Center 1
Application Load Balancer
Server
1
Server
2
LTM
Data Center 2
Rule A
Load Balancing
Setup 1 includes
DC1 & DC2
Rule B
Load Balancing
Setup 2 includes
DC3 & DC4
1 Client makes a request to view a
landing page or marketing website
2 That request gets
matched to Rule B that
includes specific URL
Path
3 Rule B is associated with Load
Balancing Setup 2 which directs traffic
to the cloud provider of choice

34. © AKAMAI - EDGE 2017
How is it different from Edge Load Balancer (ELB)?
Application Load Balancer Edge Load Balancer
Simple Setup ✔ ✘
Self Serviceable ✔ ✘
General Availability ✔ ✘

35. © AKAMAI - EDGE 2017
How is it different from Global Traffic Manager (GTM)?
Application Load
Balancer
Global Traffic Manager
Policy-based routing/
Path routing
✔ ✘
Near zero configuration ✔ ✘
Affinity and Sticky sessions* ✔ ✘
Automatic Request Retry ✔ ✘
*Session Stickiness - As a DNS solution, GTM has no
concept of HTTP headers or cookies typically used for

36. © AKAMAI - EDGE 2017
UI DEMO

37. © AKAMAI - EDGE 2017
Step 1: Create your ALB policy

38. © AKAMAI - EDGE 2017
Step 2: Add the policy to your Akamai Configuration

39. © AKAMAI - EDGE 2017
Step 3: Define your Data Centre endpoints

40. © AKAMAI - EDGE 2017
Step 4: Define your Load Balancing Setup

41. © AKAMAI - EDGE 2017
Step 5: Update your ALB policy

42. © AKAMAI - EDGE 2017
Live Demo @ Developer Zone
We have a live demo available at the Developer Zone.

43. © AKAMAI - EDGE 2017