Microservice Architecture
Supported by KongMicroservice Architecture Glossary
A work-in-progress definition of terms that are not expressed as patterns.
API
A service’s reason for existing. It consists of:
- Zero or more operations
- Zero or more published domain events
Command
A command is an operation that mutates data.
Component
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.
DORA metrics
Developed by the authors of Accelerate, the DORA metrics measure the performance of a software development teams:
- Deployment frequency - the frequency with which software changes are deployed to production.
- Lead time for changes - the time it takes to go from commit to deploy.
- Time to restore service - the time it takes to restore service after a production incident or outage.
- Change failure rate - the percentage of production deployments that result in a failure or require remediation.
Modular monolith
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).
Monolithic architecture
An architectural style that structures the application as a single executable/deployable component. See the Monolithic architecture pattern for more details.
Microservice architecture
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.
Operation
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.
Pattern
A pattern is a “reusable solution to a problem that occurs in particular context”. Read more
Query
A query is an operation that retrieves data.
Service
Each service is an element of the Microservice Architecture that is:
- Loosely coupled with other services
- Independently deployable - it an independently deployable/executable component, such as a WAR file, executable JAR, EAR file, OSGI Bundle, or operating System executable
- Owned by a small, cross-functional team
A service has an API.
System operation
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.
glossary
About Microservices.io
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.
MICROSERVICES 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 moreLEARN about microservices
Chris offers numerous other resources for learning the microservice architecture.
Get the book: Microservices Patterns
Read Chris Richardson's book:
Example microservices applications
Want to see an example? Check out Chris Richardson's example applications. See code
Remote consulting session
Got a specific microservice architecture-related question? For example:
- Wondering whether your organization should adopt microservices?
- Want to know how to migrate your monolith to microservices?
- Facing a tricky microservice architecture design problem?
Consider signing up for a two hour, highly focussed, consulting session.
Virtual bootcamp: Distributed data patterns in a microservice architecture
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.
Learn how to create a service template and microservice chassis
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
BUILD microservices
Consulting services
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
The Eventuate platform
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.
ASSESS your architecture
Consulting services
Engage Chris to conduct an architectural assessment.
Join the microservices google group
Topics
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
