There is no such thing as a microservice! · 2018-01-18 · Technology stack becomes increasingly obsolete BUT A rewrite is not feasible-ilities of large monoliths Maintainability

@crichardson

There is no such thing as a microservice!

Chris Richardson

Founder of Eventuate.io Founder of the original CloudFoundry.com Author of POJOs in Action

@crichardson [email protected] http://microservices.io http://eventuate.io http://plainoldobjects.com

Copyright © 2017. Chris Richardson Consulting, Inc. All rights reserved

@crichardson

Presentation goal

Define the Microservice Architecture

as an architectural style

Explain what that means and why it

matters

@crichardson

About Chris

@crichardson

About Chris

@crichardson

About Chris

@crichardson

About Chris

@crichardson

About Chris

@crichardson

About Chris

Consultant and trainer focusing on modern

application architectures including microservices

(http://www.chrisrichardson.net/)

http://www.chrisrichardson.net/

@crichardson

About Chris

Founder of a startup that is creating an open-source/SaaS platform

that simplifies the development of transactional microservices

(http://eventuate.io)

http://eventuate.io

@crichardson

About Chris

http://learnmicroservices.io

40% off ctwcodefreeze18


@crichardson

Agenda

A brief refresher on software architecture

From monolith to microservices

Microservices != silver bullet

Applying the microservice pattern language

@crichardson

Agenda





About software architecture

“The software architecture of a computing system is the set of structures needed to reason about the system, which comprise software elements, relations among

them, and properties of both.”

Documenting Software Architectures, Bass et al

@crichardson

Architecture =

(elements, relations, properties)

@crichardson

Architecture =

Boxes and lines 😄

@crichardson

Architecture is multi-dimensional e.g. Structural, electrical, plumbing,

mechanical

@crichardson


mechanical⇒

Described by multiple views

@crichardson


mechanical⇒

Described by multiple views

View = (elements, relations, properties)

4+1 view model

Logical View

Process View

Deployment View

Implementation View

Scenarios

4+1 Logical view

Logical View

Process View

Deployment View

Implementation View

Scenarios

Elements: classes and packages Relations: inheritance, associations, …

4+1 Implementation view

Logical View

Process View

Deployment View

Implementation View

Scenarios

Elements: modules and components Relations: dependencies

4+1 Process view

Logical View

Process View

Deployment View

Implementation View

ScenariosElements: processes Relations: IPC

4+1 Deployment view

Logical View

Process View

Deployment View

Implementation View

ScenariosElements: “machines” Relations: networking

4+1 Scenarios

Logical View

Process View

Deployment View

Implementation View

ScenariosDerived from use cases/stories

Animate the views

@crichardson

""… An architectural style determines the vocabulary of components and

connectors that can be used in instances of that style, together with a set of constraints on how they can be

combined….. ”” David Garlan and Mary Shaw, An Introduction to Software Architecture

@crichardson

Layered architectural style

@crichardson

Layered architectural styleLayer N

Layer N - 1

Layer N - 2

Well defined responsibilities

Constrained dependencies

Uses Uses

UsesUses

The role of architecture

Requirements =

Functional requirements +

Non-functional requirements (-ilities)

Domain knowledge

Architecture

Important -ilitiesMaintainability

Testability

Deployability

Evolvability

Scalability

Security

Reliability

…

https://en.wikipedia.org/wiki/Non-functional_requirement


Testability

Deployability

Evolvability

Scalability

Security

Reliability

…


Sunday afternoon 😀


Testability

Deployability

Evolvability

Scalability

Security

Reliability

…


Development velocity

Sunday afternoon 😀

@crichardson

Businesses must innovate faster ⇒

Build better software faster

@crichardson

Reducing lead time

Increasing deployment frequency

@crichardson

Modern software development: moving fast and not breaking things!

46x

440x

24x

5x lower

Amazon: ~0.001%

Netflix: 16 minutes

@crichardson

Modern software development

Architecture:

Process:

Small, autonomous teams

???

DevOps/Continuous delivery/deployment

Organization:

Agenda





@crichardson

Traditional: Monolithic architecture

Review Management

Catalog Management

Recommendation Management

StoreFrontUI

Order Management

Logical view

@crichardson

Tomcat/App. Server

Traditional: Monolithic architecture

Browser/Client

WAR/EAR

MySQL Database

Review Management

Catalog Management

Recommendation Management

StoreFrontUI

Order Management

HTMLREST/JSON

Logical viewImplementation view

@crichardson

The monolithic architecture is an architectural style

that structures the application as a single executable

component

Implementation view

-ilities of small monoliths

Maintainability

Testability

Deployability

…


😄

@crichardson

But successful applications keep growing….

Development Team Application

@crichardson



@crichardson



@crichardson



@crichardson

… and growing

Development Team A

ApplicationDevelopment Team B

Development Team C

@crichardson

Eventually:

agile development

and deployment becomes

impossible

=

monolithic hell

@crichardson

Technology stack becomes increasingly obsolete

BUT A rewrite is not feasible

-ilities of large monoliths

Maintainability

Testability

Deployability

…


😭

The microservice architecture is an architectural style

that structures an application as a

set of loosely coupled, services organized around

business capabilities

@crichardson

Service = business capabilityAcme, Inc

Order Taking

Inventory management

Delivery management

Business Capability = something a business does to deliver value

…

@crichardson

Application

Service = business capabilityAcme, Inc

Order Taking

Inventory management

Delivery management

Business Capability = something a business does to deliver value

…

Order Service

Inventory Management

Service

Delivery Management

Service … Service

@crichardson

Service = independently deployable component

CommandQuery

API

EventPublisher

EventSubscriber

APIClient

Consumer facing Implementation

Synchronous: REST, gRPC, …Asynchronous: Command/Reply, Notification

Service database

EventsEvents

Synchronous: REST, gRPC, …

Asynchronous: Command/Reply, Notification

Data owned by the service

Data replicated from elsewhereSLA

Service size is secondary

microservice architecture

Service:

Meaningful business functionality

Developed by a small team

Minimal lead time/high deployment frequency

Microservices =

Microservice architecture =

Application architecture ⇒

No such thing as a microservice

@crichardson

@crichardson

Catalog Service

Review Service

Order Service

… Service

@crichardson

Catalog Service

Review Service

Order Service

… Service

Catalog Database

Review Database

Order Database

… Database

@crichardson

Browser Content Router

Catalog Service

Review Service

Order Service

… Service

Catalog Database

Review Database

Order Database

… Database

HTTP /HTML

Browse & Search WebApp

Product Detail WebApp

….

@crichardson

Browser Content Router

API Gateway

Catalog Service

Review Service

Order Service

… Service

Catalog Database

Review Database

Order Database

… Database

HTTP /HTML



….

@crichardson

Browser

Mobile Device

Content Router

API Gateway

Catalog Service

Review Service

Order Service

… Service

Catalog Database

Review Database

Order Database

… Database

HTTP /HTML

REST

REST



….

@crichardson

Browser

Mobile Device

Content Router

API Gateway

Catalog Service

Review Service

Order Service

… Service

Catalog Database

Review Database

Order Database

… Database

HTTP /HTML

REST

REST



….

Supplier Inbound Gateway

Catalog update messages

Supplier System

-ilities of a microservice architecture

Maintainability

Testability

Deployability

…


😄

@crichardson

Microservices ⇒

DevOps/Continuous delivery/deployment of large/complex applications

@crichardson

Process: Continuous delivery/deployment

Organization:Small, agile, autonomous,

cross functional teams

Architecture: Microservice architecture

Enables

Enables Enables

SuccessfulSoftware

Development

@crichardson





Enables

Enables Enables

SuccessfulSoftware

Development

Services improve testability

and deployability

@crichardson





Enables

Enables Enables

SuccessfulSoftware

Development

Services improve testability

and deployability

Teams own services

@crichardson

Microservices ⇒ evolve the technology stack

Pick a new technology when

Writing a new service

Making major changes to an existing service

Let’s you experiment and fail safely

@crichardson

Agenda





@crichardson

No silver bullets

http://en.wikipedia.org/wiki/Fred_Brooks

@crichardson

Drawbacks of microservices

Complexity

@crichardson


Complexity

Development: IPC, partial failure, distributed data

@crichardson


Complexity

Development: IPC, partial failure, distributed data Testing: Integration, end to end, …

@crichardson


Complexity

Development: IPC, partial failure, distributed data Testing: Integration, end to end, …Deployment …

@crichardson

Are microservices a good fit for my application?

@crichardson

Do I have the pre-requisites in place:

automated testing automated provisioning ….. ?

@crichardson

When using microservices:

@crichardson

When using microservices:How to decompose an application into services?

How to deploy an application’s services?How to handle cross cutting concerns?

Which communication mechanisms to use?

How do external clients communicate with the services?

How does a client discover the network location of a service instance?

How to prevent a network or service failure from cascading to other services?

How to maintain data consistency and implement queries?

How to make testing easier?

How to understand the behavior of an application and troubleshoot problems?

How to implement a UI screen or page that displays data from multiple services?

@crichardson

It depends!

@crichardson

Microservice pattern language =

collection of patterns that solve these

architecture, design, development and operational problems

@crichardson

What’s a pattern?

Reusable solution to a problem

occurring in a particular context

@crichardson

What’s a pattern?

Reusable solution to a problem

occurring in a particular context

@crichardson

The structure of a pattern encourages objectivity

@crichardson


Name

@crichardson


aka the situation

Name

Context

@crichardson


aka the situation

Name

Context

Problem

@crichardson


aka the situation

Name

Context

Problem

(conflicting) issues etc to address Forces

@crichardson


aka the situation

Name

Context

Problem


Solution

@crichardson


Resulting context

aka the situation

Name

Context

Problem


Solution

@crichardson


Resulting context

aka the situation

Name

Context

Problem


Solution Benefits

@crichardson


Resulting context

aka the situation

Name

Context

Problem


Solution Benefits

Drawbacks

@crichardson


Resulting context

aka the situation

Name

Context

Problem


Solution Benefits

Drawbacks

Issues to resolve

@crichardson


Resulting context

aka the situation

Name

Context

Problem

Related patterns


Solution Benefits

Drawbacks

Issues to resolve

@crichardson


Resulting context

aka the situation

Name

Context

Problem

Related patterns


Solution Benefits

Drawbacks

Issues to resolve

Alternatives

@crichardson


Resulting context

aka the situation

Name

Context

Problem

Related patterns


Solution Benefits

Drawbacks

Issues to resolve

Alternatives

Solutions to issues

@crichardson

Microservices pattern language: http://microservices.io

http://microservices.io

@crichardson

Agenda





@crichardson

The pattern language guides you when developing an architecture

What architectural decisions you must make

For each decision:

Available options

Trade-offs of each option

@crichardson

Key patterns

Issue: What’s the deployment architecture?

Forces

Maintainability

Deployability

Testability

…

Monolithic architecture

Microservice architecture


Forces

Maintainability

Deployability

Testability

…



Single deployable/executable OR

Tightly coupled services


Forces

Maintainability

Deployability

Testability

…



Single deployable/executable OR

Tightly coupled services

Multiple loosely coupled services

Issue: How to decompose an application into services?

Forces

Stability

Cohesive

Loosely coupled

Not too large

Decompose bybusiness capability

Decompose bysubdomain


Forces

Stability

Cohesive

Loosely coupled

Not too large



Organize around business capabilities


Forces

Stability

Cohesive

Loosely coupled

Not too large



Organize around business capabilities

Organize around DDD subdomains

@crichardson

Issue: how to maintain data consistency?Context

• Each service has its own database

• Data is private to a service

Forces

Transactional data consistency must be maintained across multiple services

2PC is not an option

@crichardson

Issue: how to perform queries?

CQRS

Context

Each service has its own database

Forces

Queries must join data from multiple services

Data is private to a service

API Composition

@crichardson

Issue: how to perform queries?

CQRS

Context

Each service has its own database

Forces

Queries must join data from multiple services

Data is private to a serviceMaintain query views by subscribing to events

API Composition

@crichardson

The rest are generic technical architecture patterns

= Undifferentiated heavy lifting!

@crichardson

Issue: How do services communicate?

Messaging Remote ProcedureInvocation

Domain-specific

Forces

Services must communicate

Usually processes on different machines

…

@crichardson

Issue: How to handle cross cutting concerns?

Microservice Chassis

Forces

Every service must implement logging; externalize configuration; health check endpoint; metrics; …

Issue: How to deploy an application’s services?

Multiple Services per host

Single Service per Host

Service-per-Container

Service-per-VM

Serverless deployment

Service deployment platform

Forces

Multiple languages

Isolated

Constrained

Monitor-able

Reliable

Efficient

@crichardson

Issue: How to discover a service instance’s network location?

Client-side discovery

Server-side discovery

Service registry

Self registration

3rd party registration

Forces

Client needs IP address of service instance

Dynamic IP addresses

Dynamically provisioned instances

@crichardson

Issue: how to monitor the behavior of your application?

Exception tracking

Distributed tracing

Audit logging Application metrics

Log aggregation

Health check API

@crichardson

Summary

The goal of architecture is to satisfy non-functional requirements

For continuous delivery/deployment use the appropriate architectural style

Small applications ⇒ Monolithic architecture

Complex applications ⇒ Microservice architecture

Use the pattern language to guide your decision making

@crichardson

@crichardson [email protected]


Thank you!

40% off ctwcodefreeze18

mailto:[email protected]

Documents

There is no such thing as a microservice! · 2018-01-18 · Technology stack becomes increasingly obsolete BUT A rewrite is not feasible-ilities of large monoliths Maintainability