23
SO YOU THINK YOU CAN S C A L E @F5Networks containers?

So you think you can scale containers

Embed Size (px)

Citation preview

Page 1: So you think you can scale containers

SO YOU THINK YOU CAN

S C A L E @F5Networks containers?

Page 2: So you think you can scale containers

Why do we scale?

Page 3: So you think you can scale containers

=

Page 4: So you think you can scale containers

100 Milliseconds Slower

-1% SALES -0.2% SEARCHES -2% CONVERSION

$660M $45M $244M

H/T James Urquhart, SOASTA Data: Gartner, Walmart

Page 5: So you think you can scale containers

1 Minute of Downtime

Data: Emerson Power

Costs an average of $7300

Average total cost of downtime per year across industries

PRODUCTIVITY IT PRODUCTIVITY LOST REVENUE

$53,608$140,543 $183,724

Page 6: So you think you can scale containers

UP OUT

How do we scale today?

Page 7: So you think you can scale containers

But architectures and apps are changing

THEN

MONOLITHIC MICROSERVICES & APIs

NOW

Page 8: So you think you can scale containers

And so are environments

THEN NOW

DATA CENTERS & SERVERS CLOUDS & CONTAINERS

Page 9: So you think you can scale containers

COMMS INCREASES EXPONENTIALLY

THEN NOW

Page 10: So you think you can scale containers

SMALLER CAPACITY MEANS MORE CLONES

THEN NOW

Page 11: So you think you can scale containers

RAPID CHANGES MAKE SCALING HARD

NOWTWO MINUTES AGO

Page 12: So you think you can scale containers

REVERSE PROXY

THEN NOW

Page 13: So you think you can scale containers

FORWARD PROXY

• NATIVE CONSTRUCT• BASED ON IP TABLES• LIMITED to IP:PORT

Page 14: So you think you can scale containers

REVERSE PROXY

• EPHEMERAL CONSTRUCT• BASED ON IP TABLES• LIMITED to IP:PORT

Page 15: So you think you can scale containers

SIDECAR PROXY

• PLUG-IN CONSTRUCT• FORWARD PROXY• L7 CAPABLE

Page 16: So you think you can scale containers

LAYER 1

LAYER 2

LAYER 3 (IP)

LAYER 4 (TCP)

LAYER 5

LAYER 6

LAYER 7 (HTTP)

LAYER 7.5 (TAGS)

LAYER 4.5 (MESH)

LAYER 2.5 (OVERLAY - VXLAN)

TRADITIONAL OSI STACKAssumes underlying protocols behave consistently and reliably. Relies on proper adherence to and reliability of lower order protocols.

CONTAINER OVERLAY STACKAssumes underlying protocols exist but are unreliable. Implements its own routing and reliability constructs to avoid failure of and reliance on lower order protocols.

BUILDING A SERVICE MESH

Page 17: So you think you can scale containers

A SERVICE MESH

Circuit breakers

Auto-Retries

A network of sidecar proxies that form a reliable method of scale that includes:

Health monitoring

HTTP Routing

Page 18: So you think you can scale containers

HTTP ROUTINGLike Google maps, but for your apps

URI & method

host

custom

Cookie

GET /path/to/my/service/with/variables

http://host.domain.xxx

request

headers

X-API-version: 1

Cookie: 09124890tlsgkq3i3KJSDLFJ)*@$#()You encrypt your cookies, right? RIGHT?!

Page 19: So you think you can scale containers

RETRIESDO OVER! • CONGESTION

• CAPACITY • FAILURE• REJECTION

Page 20: So you think you can scale containers

CIRCUIT BREAKERSSTOP TRYING ALREADY

Page 21: So you think you can scale containers

MONITORINGIF I’M NOT HOME, DO YOU STILL DRIVE TO MY HOUSE?

Service is unavailable

Service is slow

Service is returning errors

Page 22: So you think you can scale containers

SCALING CONTAINERSSMARTER and FASTER : SERVICE MESH

Must be L7 (HTTP) fluent

Delegate instead of dictate

Monitoring is not optional

Collaborative not constant

Page 23: So you think you can scale containers

THANK YOU!@F5Networks