xconf coimbatore 2016 - microservices demystified

MicroservicesDemystified

Selvakumar Natesan

What are Microservices?

Typical application


Monoliths


Microservices

* Each element as its own service


Microservices


Small autonomous services that work together

- Sam Newman


SOA ?ESB

(proprietary tools)

Heavy Integration (like WCF, SOAP, JBI)

Hard to test

Technical service boundaries

Business Contract as boundaries

Lightweight transport (like http/json)


service-oriented architecture composed of loosely coupled elements that have

bounded contexts- Adrian Cockcroft

Microservices


Microservices

Write programs that do one thing and do it well. Write programs to work together

- The Unix Way


Characteristics of a Microservice Architecture

> Componentization via Services > Organized around Business Capabilities > Products not Projects > Smart endpoints and dumb pipes > Decentralized Governance > Decentralized Data Management > Infrastructure Automation > Design for failure > Evolutionary Design

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


Componentization via Services

http/json

async / messaging

CommunicationService

OrderService

CatalogService

http/json

RecommendationService

Characteristics of a Microservice

Organized around Business Capabilities

Presentation

Business Logic

Data Access / DB



Catalog

Order

Shipping

Bounded Context



Catalog

Order

Shipping


"organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these

organizations" —Melvin Conway

Products, Not Projects


Catalog

Team own end to end From technical choices to deployment

{ "id": "iphone-6s-16gb", "specification": { "...": "..." }, "price": 35000, "currency": "₹", "...": "..."}

Smart endpoints and dump pipes


Catalog

Order

Communication

RESTful(http / json)

/items/iphone-6s-16gb


Catalog

Order

Decentralized Governance

Communication


Catalog

Order

Communication

Decentralized Data Management

Infrastructure Automation


> builds > tests - unit, integration, end to end, performance > provisioning > deployment

> from test environment > to production

Infrastructure Automation


Design for failure


> Tolerate the failure of services > Timeouts, retries and circuit breaker patterns > Real-time monitoring > Log aggregation

Evolutionary Design


> Build few bigger services first > Then, slowly peel off different services > Based on independent replacement and upgradeability > Make granular releases

Characteristics of a Microservice Architecture

> Componentization via Services > Organized around Business Capabilities > Products not Projects > Smart endpoints and dumb pipes > Decentralized Governance > Decentralized Data Management > Infrastructure Automation > Design for failure > Evolutionary Design



Are you ready for Microservices?

Readiness for microservices

Are you ready for Microservices?> Operational Complexity due to distribution > Tolerance for Eventual consistency > Automated Testing (Test Pyramid) > Automated Build and Deployment > Rapid Provisioning > Monitoring needs > Remote calls – expensive

Avoid microservices envy

Readiness for microservices http://martinfowler.com/bliki/MicroservicePremium.html

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

Readiness for microservices

Microservice architectures provide unique benefits at the cost of increased (essential)

complexity.

Want to know more?martinfowler.com/microservices

Building Microservices

Domain-Driven Design

Implementing Domain-Driven Design

Release It!

http://martinfowler.com/microservices

Thank you!

Selvakumar Natesan@selvakn

#XConf #Coimbatore

Who are all doing Microservices?

xconf coimbatore 2016 - microservices demystified

Technology