A Capability Blueprint for Microservices

September 13, 2016

MicroservicesA Capability Blueprint

Matt McLartyVice President, API AcademyCA Technologies@mattmclartybc

2

Why are organizations using microservices?

3

Business Value Stories

“We can scale our operation independently, maintain unparalleled system availability, and introduce new services quickly without the need for massive reconfiguration.”

•Werner Vogels, Amazon (2006) https://queue.acm.org/detail.cfm?id=1142065

“…the next generation [architecture] that we are building will give Netflix a strong foundation to meet the needs of our massive and growing scale, enabling us to delight our global audience.”

•Netflix (2015) http://techblog.netflix.com/2015/01/netflixs-viewing-data-how-we-know-where.html

“Lessens dependencies between teams - resulting in faster code to production.”

•Adrian Trenaman, Gilt (2015) http://www.infoq.com/news/2015/04/scaling-microservices-gilt

“With the new architecture framework, we were able to reduce our lead time for new features to something that…was much more acceptable for a company trying to play in the highly competitive music industry.”

•Phil Calçado, SoundCloud (2015) http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html

https://queue.acm.org/detail.cfm?id=1142065

http://techblog.netflix.com/2015/01/netflixs-viewing-data-how-we-know-where.html

http://www.infoq.com/news/2015/04/scaling-microservices-gilt

http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html

4

The goal of microservices

Speed and safety at scale

5

Microservice Architecture Maturity Model

Speed Safety

Sca

le &

Co

mp

lexi

ty

6


Independent Deployability

Polyglotism

Independent Manageability

Testability

Modularized“Establish the foundation”

Speed Safety

A microservice architecture that is…

Sca

le &

Co

mp

lexi

ty

7



Polyglotism


Testability

Organizational Alignment

Composability

Replaceability

Efficiency


Cohesive“Design the services”

Speed Safety


Sca

le &

Co

mp

lexi

ty

8



Polyglotism


Testability


Composability

Replaceability

Efficiency

Agility

Comprehensibility

Resiliency/ Availability

Runtime Scalability


Cohesive“Design the services”

Systematized“Design the system”

Speed Safety


Sca

le &

Co

mp

lexi

ty

9

Benefits of Modularization


Polyglotism


Testability

10



Polyglotism


Testability

Supporting Capabilities

Containers CI/CDConfiguration Management

Platform Hosting (IaaS, PaaS)

11



Polyglotism


Testability


Containers APIs



Multi-Language Platform Hosting

12



Polyglotism


Testability


Containers Platform Hosting

Containers APIs



APIs Logging


13



Polyglotism


Testability


Containers Platform Hosting

Containers APIsContract

DefinitionService

Virtualization

Containers APIs



APIs Logging


14

Benefits of Cohesion


Composability

Replaceability

Efficiency

15



Composability

Replaceability

Efficiency


Domain-oriented APIs

Business Analytics

Business Alignment

Organizational Design

16



Composability

Replaceability

Efficiency


Loosely-coupled APIs

ContainersComponent

RegistryTeam

Autonomy


Business Analytics

Business Alignment


17



Composability

Replaceability

Efficiency


APIs ContainersTeam

AutonomyChange

Tolerance


ContainersComponent

RegistryTeam

Autonomy


Business Analytics

Business Alignment


18



Composability

Replaceability

Efficiency


APIs ContainersTeam

AutonomyChange

Tolerance

ContainersPlatform Hosting

Component Registry

Business Alignment


ContainersComponent

RegistryTeam

Autonomy


Business Analytics

Business Alignment


19

Benefits of Systematization

Agility

Comprehensibility


Runtime Scalability

20


Agility

Comprehensibility


Runtime Scalability


Component Registry

AutomationAgile Software Development

Iterative Approach

21


Agility

Comprehensibility


Runtime Scalability



Contract Definition

Small TeamsCross-Org Visibility

Component Registry


Iterative Approach

22


Agility

Comprehensibility


Runtime Scalability


Monitoring AutomationCross-Org Visibility

Change Tolerance


Contract Definition


Component Registry


Iterative Approach

23


Agility

Comprehensibility


Runtime Scalability


Monitoring AutomationCross-Org Visibility

Change Tolerance

Operational Analytics

Component Registry

Cross-org Visibility

Team Autonomy


Contract Definition


Component Registry


Iterative Approach

24

Microservices Technological Capabilities

Monitoring Capabilities

Container Repository & Management

App Performance Monitoring

End User Experience Monitoring

System Monitoring &

Recovery

Business & IT Analytics Capabilities

Business Analytics

Event Monitoring &

Execution

Operational Analytics

Continuous Business Planning

Mobile Apps Web Apps Other Microservices

Consumers

Logging

Design & Development Capabilities

Container & Image Creation

μS & API Design

μS Development Framework

μS Test Management &

Automation

Component Registry/Discovery

Contract DefinitionUser Analytics

Mediation Capabilities Policy Enforcement (Security, SLA, Audit, Regulatory)

PlatformCapabilities

Infrastructure-as-a-Service

Platform-as-a-Service

Functions-as-a-Service

Microservices

Configuration & Deployment Capabilities Container Management

Continuous Delivery / Release Management

Configuration Management

Routing/ Aggregation

Messaging/Content

Security Capabilities Authentication & Authorization

Identity Management

Service Discovery / Registration

Client App Capabilities(Mobile, web, IoT apps)

Service Virtualization

μS Client Development

IoT Devices

Mobile Monitoring

Container Hosting

25

Microservices Non-Technological Capabilities

Methodological Capabilities

Agile software development

Continuous integration/continuous delivery (build & deployment automation)

Test automation

Operational automation

Organizational Capabilities

Small team size

Business alignment

Cross-organizational supporting teams

“Guilds”

Organizational design

Cultural Capabilities

Stated principles

Team autonomy and empowerment

Two way communication

Change tolerance

Experimental and iterative approach

Toolmaking and enablement (vs. “governance”)

26

In summary…

Early microservice adopters seek speed and safety at scale

Three levels of microservice architectures:

• Modularized

• Cohesive

• Systematized

Each level brings different benefits

Microservice capabilities enable the benefits

27

For more information…

Microservice Architecture, from O’Reilly Media

• http://transform.ca.com/API-microservice-architecture-oreilly-book.html

Videos from #API360 Microservices Summit (NYC, 6/16/16)

• http://transform.ca.com/API-Microservices-Best-Practices-API360-Summit-Videos.html

Infoworld Series on Microservices

• http://www.infoworld.com/article/3075880/application-development/microservice-architecture-is-agile-software-architecture.html

• http://www.infoworld.com/article/3080611/application-development/learning-from-soa-5-lessons-for-the-microservices-era.html

O’Reilly Blog Series

• https://www.oreilly.com/ideas/optimize-for-desirable-results

• https://www.oreilly.com/ideas/microservices-need-architects

• https://www.oreilly.com/ideas/microservices-shift-complexity-to-where-it-belongs

• https://www.oreilly.com/ideas/three-pillars-of-microservice-culture

http://transform.ca.com/API-microservice-architecture-oreilly-book.html

http://transform.ca.com/API-Microservices-Best-Practices-API360-Summit-Videos.html

http://www.infoworld.com/article/3075880/application-development/microservice-architecture-is-agile-software-architecture.html

http://www.infoworld.com/article/3080611/application-development/learning-from-soa-5-lessons-for-the-microservices-era.html

https://www.oreilly.com/ideas/optimize-for-desirable-results

https://www.oreilly.com/ideas/microservices-need-architects

https://www.oreilly.com/ideas/microservices-shift-complexity-to-where-it-belongs

https://www.oreilly.com/ideas/three-pillars-of-microservice-culture

28

Thank you!