Microservice Architecture
Supported by KongThe developer’s essential knowledge pyramid
Developing software is difficult. It requires a lot of knowledge. But understanding today’s fashionable technology is insufficient. You also need to understand numerous concepts, principles and practices. But above all, you must have deep understanding of the problem domain. In other words, you need to understand all three layers of the developer knowledge pyramid.
The problem domain
Developers often like to describe themselves in terms of technologies, principles and practices. Today, for example, a fashionable description might be “Socio-technical, full-stack, Java 17 developer”. But while principles and practices are part of the developer knowledge pyramids, it’s far more important to understand the problem domain. If you don’t understand the problem domain, your technical skills are irrelevant. Your perfectly engineered solution will be a failure.
Development concepts, principles and practices
In addition to understanding the problem domain, a developer also needs to numerous (and timeless) concepts, principles and practices. For example:
- Design principles, such as modularity and encapsulation
- Database transaction management concepts such as the meaning of ACID, isolation levels, etc and how to use them
- Design practices, such as evaluating the benefits and drawbacks are possible solutions and selecting the most appropriate one
- Development practices, such as continuous delivery, automated testing, etc.
- …
Without mastering these development concepts, principles and practices, you will most likely be unproductive and develop software that’s poorly designed, unmaintainable and buggy.
Technology
Last and some what least, you need to understand technology. This includes your application’s technology stack (languages, libraries, and frameworks) and the tools that you use to develop, test and deploy it. It’s not good enough to only have a fuzzy understanding of a technology and use it by trial and error. You need to read the manual and have solid mental model of how it works.
An alternative metaphor: developer knowledge tripod
This was based on some interesting feedback on LinkedIn. Perhaps this is a better metaphor:
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
