keynote: architecting for continuous delivery (pivotal cloud platform roadshow)

1 © Copyright 2013 Pivotal. All rights reserved. 1 © Copyright 2014 Pivotal. All rights reserved.

Architecting for Continuous Delivery

Microservices with Pivotal CF and Spring Cloud

© Copyright 2014 Pivotal. All rights reserved.

What is Continuous Delivery?

2

$Busin

ess

Devel

opm

ent

QA

Ope

ratio

nsCu

stom

er


What is Continuous Delivery?

3

$

© Copyright 2014 Pivotal. All rights reserved. 4

Continuous Delivery - How?


Warner Music: Software FactoriesWarner Software Factory Platform • New applications and major updates

- Before: 6 months, team of 10 developers - After: 6 weeks, same team - Speed/Agility: 400% faster on new platform - HR Hard Savings: $1.1M per application update

delivered


Iterative Development

Design Develop

Test

Customer Feedback Customer

Delivery

Analytics


Horizontal Scale

7

Slow/Expensive Fast/Cheap


Diversity of Clients

8

http://money.cnn.com/2014/02/28/technology/mobile/mobile-apps-internet/

In January 2014, mobile devices accounted for 55% of Internet usage in the United States. Apps made up 47% of Internet traffic and 8% of traffic came from mobile

browsers.


InfrastructureApplications

MonolithsMicroservices

Physical/Virtual Pivotal CFContinuous Delivery

Software Factories

Feedback Rapid Iteration

Horizontal Scale

Diversity of Clients


New Architectural Constraints• Pivotal CF optimizes for 12 Factor Linux applications


Twelve Factors•One Codebase/Many Deploys

• Explicit Isolated Dependencies

•Config via Environment

•Attached Backing Services

• Separate Build/Release/Run

• Stateless Processes

• Export Services via Port Bindings

• Scale Out via Processes

•Disposable Instances

•Dev/Prod Parity

• Logs == Event Streams

•Admin Tasks == Processes

http://12factor.net


New Architectural Constraints• Pivotal CF optimizes for 12 Factor Linux applications

•Microservices: a radical departure from traditional monolithic applications

• In both cases, the enterprise is forced to “think different.”


How XP Practices Support Each Other

13

http://www.kusmin.eu/wiki/index.php/How_XP_Practices_Support_Each_Other


A Mutualistic Symbiotic Relationship…

14

Microservices

http://en.wikipedia.org/wiki/Symbiosis#Mutualism

Pivotal CF

© Copyright 2014 Pivotal. All rights reserved.© Copyright 2014 Pivotal. All rights reserved.

Microservices Overview

15


Simple vs. Easy• Simple

• sim- plex

• one fold/braid

• vs complex

• Easy

• ease < aise < adjacens

• lie near

• vs hard


Monolithic Architecture

17

Relational Database

Data Access

Service

HTML JavaScript MVC

Service

Monolithic ApplicationBrowser


Monolithic Architectures•Complex / Easy

•Modularity Dependent Upon Language / Frameworks

•Change Cycles Tightly Coupled / Obstacle to Frequent Deploys

• Inefficient Scaling

•Can Be Intimidating to New Developers

•Obstacle to Scaling Development

• Requires Long-Term Commitment to Technical Stack


Microservice Architecture

19

…

HTTP

HTTP

HTTP

HTTP

HTTP

HTTP

AMQPAMQP

Relational DB

Key/Value Store

Graph DB


Microservice Architectures• Simple / Hard

•Modularity Based on Component Services

•Change Cycles Decoupled / Enable Frequent Deploys

• Efficient Scaling

• Individual Components Less Intimidating to New Developers

• Enables Scaling of Development

• Eliminates Long-Term Commitment to Technical Stack


Conway’s Law

21

Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.

Melvyn Conway, 1967

http://martinfowler.com/articles/microservices.html#OrganizedAroundBusinessCapabilities


Organize Around Business Capabilities

22

Data Access

Service

HTML JavaScript MVC

Service

UI S

pecialists

Middlew

are S

pecialists

DB

As

Business C

apability

Business C

apability

Business C

apabilitySiloed Functional Teams

http://martinfowler.com/articles/microservices.html#OrganizedAroundBusinessCapabilities

Siloed Application Architectures

Cross- functional Teams

Microservice Architectures


Partitioning Strategies•By Noun (e.g. product info service)

•By Verb (e.g. shipping service)

• Single Responsibility Principle(http://programmer.97things.oreilly.com/wiki/index.php/The_Single_Responsibility_Principle)

•Bounded Context (http://martinfowler.com/bliki/BoundedContext.html)

http://programmer.97things.oreilly.com/wiki/index.php/The_Single_Responsibility_Principle

http://martinfowler.com/bliki/BoundedContext.html


Bounded Contexts

24

Movie Movie

Actor

Genre

Media Type

Media Type

Kiosk

Location

Media

Product Catalog

Inventory


Polyglot Persistence

25

REST XYou shall not pass…


UNIX Pipes and Filters

cut -d" " -f1 < access.log | sort | uniq -c | sort -rn | less


Choreography over Orchestration

27

https://www.flickr.com/photos/gabrielsaldana/5896491978

https://www.flickr.com/photos/chrisbrenschmidt/2223763842

http://martinfowler.com/articles/microservices.html#SmartEndpointsAndDumbPipes

© Copyright 2014 Pivotal. All rights reserved.© Copyright 2014 Pivotal. All rights reserved. 28

http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html


Paying for your lunch…• Significant Operations Overhead

• Substantial DevOps Skills Required

• Implicit Interfaces

•Duplication of Effort

•Distributed System Complexity

•Asynchronicity is Difficult!

• Testability Challenges


You must be this tall to use Microservices…

30

http://martinfowler.com/bliki/MicroservicePrerequisites.html

https://www.flickr.com/photos/gusset/3723961589

• RAPID PROVISIONING

•BASIC MONITORING

• RAPID APPLICATION DEPLOYMENT

•DEVOPS CULTURE


It’s gonna take a platform…

31

Pivotal CF Spring Cloud


Platform Features

• Environment Provisioning

•On-Demand/Automatic Scaling

• Failover/Resilience

• Routing/Load Balancing

•Data Service Operations

•Monitoring

•Distributed/Versioned Config

• Service Registration/Discovery

• Routing/Load Balancing

• Service Integration

• Fault Tolerance

•Asynchronous Messaging


http://projects.spring.io/spring-cloud


• Eureka

•Hystrix + Turbine

• Ribbon

• Feign

• Zuul

•Archaius

+

http://netflix.github.io


Pivotal CF + Spring Cloud + Netflix OSS!

35


DEMO


Supporting Rapid Change

37

Microservices is the first architectural style developed:

POST

POST&

Continuous Delivery

DevOps∆


Architecture is abstract until it is operationalized.

Neal Ford


Architectures that aren’t operationalized exist only on whiteboards.

Matt Stine


OPERATIONALIZED ARCHITECTURE

40

Microservices

Pivotal CF

Spring Cloud

A NEW PLATFORM FOR A NEW ERA