Principles of microservices velocity

PRINCIPLES OF MICROSERVICESSam Newman Velocity Santa Clara, May 2015

1

@samnewman@velocityconf


Sam Newman

Building MicroservicesDESIGNING FINE-GRAINED SYSTEMS


Accounts

Returns

Invoicing

Shipping

Inventory

Customer Service


Accounts

Returns

Invoicing

Shipping

Inventory

Customer Service

Small Autonomous services that work together

@samnewman@velocityconf5

Show Gilt, Groupon, Netflix, Amazon

@samnewman@velocityconf http://www.12factor.net/

http://www.12factor.net/


Strategic Goals Architectural

Principles Design and Delivery

Practices

Enable scalable business More customers/transactions Self-service for customers

Support entry into new markets Flexible operational processes New products and operational processes

Support innovation in existing markets Flexible operational processes New products and operational processes

Reduce inertia Make choices that favour rapid feedback and change, with reduced dependencies across teams.

Eliminate accidental complexity Aggressively retire and replace unnecessarily complex processes, systems, and integrations so that we can focus on the essential complexity.

Consistent interfaces and data flows Eliminate duplication of data and create clear systems of record, with consistent integration interfaces.

No silver bullets Off the shelf solutions deliver early value but create inertia and accidental complexity.

Standard REST/HTTP

Encapsulate legacy

Eliminate integration databases

Consolidate and cleanse data

Published integration model

Small independent Services

Continuous deployment

Minimal customisation of COTS/SAAS


Small Autonomous services that work together


Principles Of Microservices



Modelled Around Business Domain




Culture Of Automation




Culture Of Automation Hide Implementation

Details





Details

Decentralise All The Things





Details


Deploy Independently





Details



Consumer First





Details


Isolate Failure Deploy Independently

Consumer First





Details



Highly Observable

Consumer First


Presentation

Business Logic

Data Access


Accounts

Returns

Invoicing

Shipping

Inventory

Customer Service

13https://www.flickr.com/photos/glimeend/5692801655/

14

Register a new customer

14


Oil Change

14


Emission Test

Oil Change

14


Emission Test

Replace Tire

Oil Change

14


Order parts

Emission Test

Replace Tire

Oil Change

14


Order parts

Emission Test

Replace Tire

Oil Change

Send an invoice

14


Order parts

Emission Test

Replace Tire

Oil Change

Send an invoiceMake a repair

14


Order parts

Emission Test

Replace Tire

Oil Change

Send an invoiceMake a repair

Contact a customer

14


Order parts

Emission TestReplace Tire

Oil Change

Send an invoice

Make a repairContact a customer

15

Customer Management

Maintenance

Inventory





Details



Highly Observable

✔

Consumer First


3 Months

2 Microservices


3 Months

2 Microservices

12 Months

10 Microservices


3 Months

2 Microservices

12 Months

10 Microservices

18 Months

60 Microservices


Infrastructure Automation



Automated Testing



Continuous Delivery

Automated Testing





Details



Highly Observable

✔ ✔

Consumer First





Hide Implementation Details



Highly Observable

✔ ✔

Consumer First


DB


DB

HIDE YOUR DATABASE

@samnewman@velocityconfhttp://martinfowler.com/bliki/images/boundedContext/sketch.png

@samnewman@velocityconfhttp://martinfowler.com/bliki/images/boundedContext/sketch.png

BOUNDED CONTEXTS


Client LibraryClient LibraryClient Library


Client Library

Client Library

Client Library


Client Library

BE CAREFUL OF CLIENT LIBRARIES

Client Library

Client Library





Details



Highly Observable

✔ ✔ ✔

Consumer First


What is autonomy?


What is autonomy?

Giving people as much freedom as possible to do the job at hand


DEVOLUTION?


SELF-SERVICE

https://www.flickr.com/photos/katsrcool/15184711908/

@samnewman@velocityconfhttp://tech.gilt.com/post/102628539834/making-architecture-work-in-microservice

SHARED GOVERNANCE


OWNER-OPERATOR

https://www.flickr.com/photos/stevendepolo/5939055612


INTERNAL OPEN SOURCE


DUMB-PIPES, SMART ENDPOINTS

Magical Mystery Bus


Magical Mystery Bus


Customer Enrolment


Create Customer

Record

Customer Enrolment


Create Customer

Record

Customer Enrolment

Create Loyalty Account


Create Customer

Record

Customer Enrolment

Dispatch Welcome Pack



Create Customer

Record

Customer Enrolment



Send Welcome Email


Create Customer

Record

Customer Enrolment



Send Welcome Email

Completed


ORCHESTRATION


Customer Service

create

ORCHESTRATION


Customer Service

create

Loyalty Bank

create

ORCHESTRATION


Customer Service

create

Loyalty Bank

create

Emailsend email

ORCHESTRATION


Customer Service

create

Loyalty Bank

create

Emailsend email

Whitemailsend package

ORCHESTRATION


CHOREOGRAPHED


CHOREOGRAPHED

Customer Servicecreate


CHOREOGRAPHED


customer created


CHOREOGRAPHED


customer created

Loyalty Bank


CHOREOGRAPHED


customer created

Loyalty Bank

Email


CHOREOGRAPHED


customer created

Loyalty Bank

Email

Whitemail


CHOREOGRAPHED


customer created

Loyalty Bank

Email

Whitemail

Reporting Dashboard


CHOREOGRAPHY OVER ORCHESTRATION





Details


Highly Observable

✔ ✔ ✔

Decentralise All The Things ✔

Consumer First


ONE SERVICE PER-HOST

Host

Service


ONE SERVICE PER-HOST

Host

Service

Host

Service Service

Service Service

VS


CONSUMER-DRIVEN CONTRACTS

Shipping Inventory



Expectations

Shipping Inventory



Expectations

Prod

Shipping Inventory


https://github.com/realestate-com-au/pact

https://github.com/realestate-com-au/pact


CO-EXIST ENDPOINTS

Customer Service

Shipping


CO-EXIST ENDPOINTS

Customer Service

Shipping

V2V1


CO-EXIST ENDPOINTS

Customer Service

Shipping

V2





Details

Isolate Failure

Highly Observable

✔ ✔ ✔


Deploy Independently✔Consumer First


DOCUMENTATION


API GATEWAYS


SERVICE DISCOVERY


HUMANE REGISTRIES





Details

Isolate Failure

Highly Observable

✔ ✔ ✔


Deploy Independently✔Consumer First✔


AVOID THE DISTRIBUTED SINGLE POINT OF FAILURE!


Strangler App


Strangler App

Legacy App

Legacy AppLegacy App


Strangler App

Legacy App

Legacy App

Requests

Legacy App


Strangler App

Legacy App

Legacy App

Requests

Legacy App

30 - 60 Concurrent Requests


Strangler App

Legacy App

Legacy App

Requests

Legacy App

30 - 60 Concurrent Requests

> 800 Concurrent Requests


Strangler App

Legacy App Legacy App Legacy App

Thread Pool


Strangler App


Thread Pool

Failing…slowly!


Strangler App


Thread Pool

Failing…slowly!

Thread-pool exhausted


Strangler App


Thread Pool

Failing…slowly!


No requests to other downstream apps


Strangler App


Thread Pool

Failing…slowly!


Requests Building Up

No requests to other downstream apps


Strangler App


Thread Pool


Strangler App


Fix Timeouts

Thread Pool


Strangler App


Fix Timeouts

Thread Pool Thread PoolThread Pool


Strangler App


Fix Timeouts

Thread Pool Thread PoolThread PoolBulkhead

Downstream Connections


Strangler App


Fix Timeouts

Thread Pool Thread PoolThread PoolBulkhead

Downstream Connections

Circuit Breakers





Details

Highly Observable

✔ ✔ ✔


Deploy Independently✔Isolate Failure✔ Consumer First✔


STATS PAGES


AGGREGATION


LOGS

AGGREGATION


LOGSSTATS

AGGREGATION


CORRELATION IDS


CORRELATION IDS

ID 8964


CORRELATION IDS

ID 8964

ID 8964

ID 8964

ID 8964

ID 8964


SEMANTIC MONITORING





Details





Details



Consumer First





Details



Highly Observable

Consumer First


Sam Newman

Building MicroservicesDESIGNING FINE-GRAINED SYSTEMS

http://buildingmicroservices.com/

http://buildingmicroservices.com/


Office Hours


Office Hours

(well, 30mins)


Office Hours

12.30pm on Thursday

(well, 30mins)


http://lanyrd.com/profile/samnewman/

http://lanyrd.com/profile/samnewman/

Sam Newman @samnewman

THANKS!

Principles of microservices velocity

Business

Transcript of Principles of microservices velocity