Microservice Architecture
Supported by KongIf the Service template and Microservice chassis are the solution, what is the problem?
Last week, I had a great interview with Sven Johann for the CaSe: Conversations about Software Engineering podcast. The topic of the interview was the Service template and Microservice chassis patterns. As part of the preparation for the interview, I reviewed the two patterns on Microservices.IO and I was surprised to see that the both patterns were missing an essential element: the problem statement. A situation that reminds me of the number 42 from The Hitchhiker’s Guide to the Galaxy.
About the Service template and Microservice chassis patterns
Here are the thumbnail definitions of the two patterns.
The Service template pattern thumbnail:
Quickly create services by cloning a service template, which is a runnable, template code base that implements the logic that is common to each service.
The Microservice chassis pattern thumbnail:
Improve maintainability of services cloned from a service template by extracting the logic from the template into a microservice chassis framework.
This diagram shows the structure that results from applying these patterns:
The key elements are as follows:
- Microservice chassis - a framework implements the bulk of the logic common to each service
- Service Template - a template codebase that uses the Microservice chassis
- Service - one or more services that are cloned from the Service Template
What problem do these patterns solve?
Both pattern descriptions contain all of the essential elements (Context, Forces, Solution, Consequences, Related pattern) of a pattern except for the problem statement. So what is a concise way of stating the problem? My first thought was a suitable problem statement would be “How can a team quickly create a new service?”. While this is simple and concise, it’s somewhat vague. What does it mean to “create a service”?
If you read the context that’s shared by the two patterns, it describes the challenges with creating and maintaining a service’s code base. In particular, how to setup up and maintain the the service’s build logic and the code that implements common cross cutting concerns. But why is that a worthwhile problem to solve?
It’s important to reduce the time spent setting up this logic, because it enables the team to quickly start working on the service’s business logic - its reason for existing. What’s more, it’s important to solve this problem in a way that simplifies the future maintenance of many services. Consequently, I thought the following is an accurate problem statement:
How can a team quickly create and setup a maintainable code base for a production-ready service so they can start developing its business logic?
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
