Pushing the DevOps Envelope

How Microservices Architecture is Expanding DevOps to the Network

Lori MacVittiePrincipal Technical Evangelist | F5

@lmacvittie

What is (are?) microservices?

MONOLITHIC MICROSERVICES

One set of services Many sets of services

So?

25% caching

86%image optimization

45%tcp multiplexing

78%SSL offloading

34% web acceleration

65% of all apps delivered are web applications

SOURCE: F5 iHealth Mar 2015

38%compression

What services?

What other services?

SOURCE: F5 iHealth Mar 2015

11%Cookie encryption

1%URL rewriting

59% X-forwarded-for

82%data path

programmability

65% of all apps delivered are web applications

Some of those services are In the app In the “network”

Cookie encryption

compression

caching

URL rewriting

load balancing

Cookie encryption

compression

Monolithic Service Architecture

Firewall

Core service

Infrastructure

App Infrastructu

re

Core (shared) network App (specific) network

UsersApps

• Low rate of change• High cost of change• Low tolerance for disruption

PRIORITY: RELIABILITY

Firewall

Core service

Infrastructure

App Infrastructure

Microservice ArchitectureCore (shared) network App (specific) network

UsersApps and Services

• Low rate of change• High cost of change• Low tolerance for disruption

PRIORITY: RELIABILITY

• High rate of change• Low cost of change• High tolerance for disruption

PRIORITY: AGILITY

Per-app service

Infrastructure

Firewall Core service Infrastructur

e

App Infrastructure

Per-appservice infrastructure

Microservice Architecture

Core (shared) network App (specific) network

Users Apps and Services

• Low rate of change• High cost of change• Low tolerance for disruption

• High rate of change• Low cost of change• High tolerance for disruption

DevOps Today

Needs DevOpsing

Some services in need of DevOps areIn the network

caching

URL rewriting

load balancing

Cookie encryption

compression

Which is a problem because

of IT professionals surveyed say that once an application completes the dev process, it takes a week or more to move into production; for 14% of those, it’s a month or more.

43PERCENT

Data: InformationWeek 2014 DevOps Survey, ESG

Organizations citing biggest challenge to application deployments is time to provision NETWORK services.

44PERCENT

Why is that?

CHANGES CAUSE SERVICE

DISRUPTION

NETWORK CHANGES ARE

SLOW

24% 22% 16% 12%

HARD TO MANAGE

CHANGES TO THE NETWORK

APPLICATION CHANGES REQUIRE

NETWORK CHANGES

Source: IDC's Why the Network Matters Survey - November, 2012

How do we fix that?

DevOps the Network Things

DevOps the Network Things• Frictionless software • Per Application deployment • Scale Out software-only • Low-cost / No-cost • APIs, SDKs and community • Integration with tools (Puppet/Chef)

Firewall Core service Infrastructur

e

App Infrastructure

Per-appservice infrastructure

Core (shared) network App (specific) network

Users Apps and Services

• Low rate of change• High cost of change• Low tolerance for disruption

• High rate of change• Low cost of change• High tolerance for disruption

DevOpsing the network leads to a microservices-friendly environment

Thank You @lmacvittie