About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action and the creator of the original CloudFoundry.com. His latest startup is eventuate.io, a microservices application platform.


Public training in Minneapolis

I'll be teaching a 2 day microservices workshop in Minneapolis in January and then keynoting at the CodeFreeze conference. Learn more


Learn more about microservices

Chris offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, and example code. Learn more


Microservices consulting and training

Chris offers a comprehensive consulting services, workshops and hands on training classes to help you use microservices effectively. Get advice


Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code


Get the book: Microservice patterns


Signup for the newsletter

A new microservices application platform that solves distributed data management problems.

Join the microservices google group

A pattern language for microservices

The beginnings of a pattern language for microservice architectures.

点击这里,访问本系列文章的中文翻译

Click here for Chinese translation of the patterns

Core patterns

Which architecture should you choose for an application?

Decomposition

How to decompose an application into services?

Deployment patterns

How to deploy an application’s services?

Cross cutting concerns

How to handle cross cutting concerns?

Communication patterns

Style

Which communication mechanisms do services use to communicate with each other and their external clients?

External API

How do external clients communicate with the services?

Service discovery

How does the client of an RPI-based service discover the network location of a service instance?

Reliability

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

  • Circuit Breaker - invoke a remote service via a proxy that fails immediately when the failure rate of the remote call exceeds a threshold

Data management

How to maintain data consistency and implement queries?

  • Database per Service - each service has its own private database
  • Shared database - services share a database
  • Saganew - use sagas, which a sequences of local transactions, to maintain data consistency across services
  • API Compositionnew - implement queries by invoking the services that own the data and performing an in-memory join
  • CQRS - implement queries by maintaining one or more materialized views that can be efficiently queried
  • Event sourcing - persist aggregates as a sequence of events
  • Transaction log tailing - publish changes captured in the database’s transaction log as messages
  • Database triggers - use triggers to capture changes made to data
  • Application events - application inserts events into a database table that is used as a message queue

Security

How to communicate the identity of the requestor to the services that handle the request?

  • Access Token - a token that securely stores information about user that is exchanged between services

Testing

How to make testing easier?

Observability

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

  • Log aggregation - aggregate application logs
  • Application metrics - instrument a service’s code to gather statistics about operations
  • Audit logging - record user activity in a database
  • Distributed tracing - instrument services with code that assigns each external request an unique identifier that is passed between services. Record information (e.g. start time, end time) about the work (e.g. service requests) performed when handling the external request in a centralized service

  • Exception tracking - report all exceptions to a centralized exception tracking service that aggregates and tracks exceptions and notifies developers.

  • Health check API - service API (e.g. HTTP endpoint) that returns the health of the service and can be pinged, for example, by a monitoring service

  • Log deployments and changesnew

UI patterns

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

  • Server-side page fragment composition - build a webpage on the server by composing HTML fragments generated by multiple, business capability/subdomain-specific web applications

  • Client-side UI composition - Build a UI on the client by composing UI fragments rendered by multiple, business capability/subdomain-specific UI components


Copyright © 2017 Chris Richardson • All rights reserved • Supported by Kong.