A work-in-progress definition of terms that are not expressed as patterns.
A service’s reason for existing. It consists of:
A command is an operation that mutates data.
A component is a software unit that is executabe or deployable. For example, a Java WAR file or executable JAR file; or an operating system executable.
Developed by the authors of Accelerate, the DORA metrics measure the performance of a software development teams:
A variant of the monolithic architecture that is organized around subdomains (e.g. business capabilities) rather than technical layers (e.g. presentation, business logic, persistence).
An architectural style that structures the application as a single executable/deployable component. See the Monolithic architecture pattern for more details.
An architectural style that structures at application as set of loosely coupled, independently deployable components (a.k.a. services). See the Microservice architecture pattern for more details.
An operation is an invocable behavior of a service. There are two types of operations: commands and queries. An operation can be invoked by a service client either synchronously or asynchronously. It might also be invoked by the passing of time, e.g. to implement a batch job.
A pattern is a “reusable solution to a problem that occurs in particular context”. Read more
A query is an operation that retrieves data.
Each service is an element of the Microservice Architecture that is:
A service has an API.
A system operation is an invocable behavior of the application. There are two types of operations: commands and queries. An operation is invoked by an application client - human via UI, or an external application - either synchronously or asynchronously. It might also be invoked by the passing of time, e.g. a batch job that is executed periodically.
In a microservice architecture, a system operation is either local or distributed. A local operation is implemented by a single service. A distributed operation is implemented by multiple collaborating services.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.Learn more
Chris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging