Reminder: Architecting microservices for fast, sustainable flow
You are receiving this email because you subscribed to microservices.io
This month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team Topologies: 9am-11am CET/4pm-7pm Korea Time, September 23th-25th, 2024
In November, I'll be teaching workshops in Berlin and Milan. If you would like me to visit your company for workshop or architecture review, please contact me.
In the previous article, Architecting monoliths for fast, sustainable flow, I described the key challenges that you will encounter when architecting a monolith for fast flow.
In this article, which, like others in this series, is based on my workshop Architecting for fast, sustainable flow: enabling DevOps and Team Topologies I describe how to architect a microservice architecture to achieve fast, sustainable flow.
About the microservice architecture
In a nutshell, the microservice architecture is an architectural style that structures an application as a collection of two or more services that are loosely design-time coupled and independently deployable.
Both loose design-time coupling and independent deployability are essential characteristics of the microservice architecture.
Essential characteristic: loose design-time coupling
Services are loosely design-time coupled when changing one service rarely requires changing to another service. This characteristic enables each team to work independently without coordinating with other teams.
Essential characteristic: independently deployable
Services are independently deployable when they are packaged as a deployable or executable unit and are production-ready after being tested in isolation. It enables each team to frequently and independently deploy their services.
Much of the benefit of microservices is derived from these two characteristics. Let’s now look at the challenges.
Architecting microservices for fast, sustainable flow
With careful design, a microservice architecture is able to satisfy the architectural requirements for fast, sustainable flow. Let’s look at the details starting with the biggest benefit of the microservice architecture: great evolvability.
Microservices simplify technology stack evolution
One of the key benefits of the microservice architecture is that it simplifies the evolution of the application’s technology stack. Each service can, in theory, have its own technology stack. This enables a team to pick the best technology for the job. But, more importantly, it means that the application’s technology stack can evolve incrementally, one service at a time, which is far less disruptive to feature delivery. Microservices also enable teams to experiment with new technologies and determine if they are a good fit for the application.
Microservices have better observability
A monolith can be instrumented so that it emits a stream of telemetry. But a valuable feature of the microservice architecture is that the telemetry is more granular. You have insight into the behavior of individual services, i.e. subdomains or business capabilities.
Microservices accelerate the deployment pipeline but …
Another key benefit of the microservice architecture is that it accelerates the deployment pipeline. Each service has its own deployment pipeline. It’s relatively small compared to the entire application. Also, a service is tested in isolation before being deployed and so the tests are much simpler and fast than end-to-end tests. As a result, the deployment pipeline will typically be very fast. Moreover, since a service is an independently deployable unit, deploying it is much simpler and faster than deploying a monolith.
There are two challenges, however, with testing and deploying services independently. The first is cultural. An organization needs to abandon the idea of testing the entire application before deploying a change to a single service. It needs to replace end-to-end testing with techniques, such as consumer driven contract testing, and canary deployments.
The second challenge is ensuring that services are truly loosely design-time coupled. Otherwise, there’s a risk of a change accidentally causing a production outage. Let’s look more at loose design-time coupling.
Creating a loosely coupled microservice architecture requires careful design
A key challenge when designing a microservice architecture is to create a loosely design-time coupled architecture. Otherwise, you will end up with a distributed monolith, where some or all services regularly change in lockstep.
Services need to resemble icebergs. Each one must have small, stable API that encapsulates the much larger implementation.
When you define an API you are essentially making a bet about the ways in which your architecture will and will not change in the future. The service APIs are the stable parts of your architecture. You are betting that they will not change, at least not very often in ways that break the clients. Coincidentally, David Parnas wrote about this exact topic in this famous 1972 paper about modularity, “On the Criteria To Be Used in Decomposing Systems into Modules”.
Defining stable APIs requires very careful design and a deep understanding of the business domain. That’s why if you are building an application for a brand new domain you should consider starting with a monolith. You can then evolve the monolith into a microservice architecture when you learn more about the domain and understand which parts are stable and which are not.
Defining stable APIs also requires an organization to abandon the myth that a microservice architecture must consist of lots of small services. The overriding concern is that services must be loosely coupled and independently deployable even if this means that services are no longer small.
Want to learn more?
As you can see, architecting microservices for fast flow requires careful design. If you want to learn how to design a fast flow architecture, enroll in my upcoming public online workshop on architecting for fast, sustainable flow.
You will learn:
- Architectural requirements for fast, sustainable flow.
- The forces that shape an architecture and the trade-offs that you will need to make when designing an architecture.
- How to decide between the monolithic and microservice architectural styles.
- How to design a microservice architecture using dark energy and dark matter.
Need help with accelerating software delivery?
I’m available to help your organization improve agility and competitiveness through better software architecture: training workshops, architecture reviews, etc.
Learn more about how I can help
Older messages
Architecting microservices for fast, sustainable flow
Tuesday, September 3, 2024
You are receiving this email because you subscribed to microservices.io This month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team
Architecting monoliths for fast, sustainable flow
Thursday, August 22, 2024
You are receiving this email because you subscribed to microservices.io Next month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team
Reminder: Why architecting for fast, sustainable flow is important
Tuesday, August 20, 2024
You are receiving this email because you subscribed to microservices.io Next month, I'm teaching an online public workshop: Architecting for fast, sustainable flow: Enabling DevOps and Team
Why architecting for fast, sustainable flow is important
Tuesday, August 20, 2024
You are receiving this email because you subscribed to microservices.io Next month, I'm teaching an online public workshop: Architecting for fast, sustainable flow: Enabling DevOps and Team
Reminder: Better architecture thru deliberative design
Thursday, August 8, 2024
Upcoming public architecture workshops You are receiving this email because you subscribed to the microservices.io mailing list. Helping organizations accelerate software delivery You are eager to
You Might Also Like
Stay compliant without compromising productivity
Thursday, November 21, 2024
Join us on December 5th ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Spyglass Dispatch: Comcast's SpinCo Out Hunting • NVIDIA Makes Mint • The Fate of Chrome • Amazon Shows New 'Show' • End of Around the Horn • Writing on the Web
Thursday, November 21, 2024
Comcast's SpinCo Out Hunting • NVIDIA Makes Mint • The Fate of Chrome • Amazon Shows New 'Show' • End of Around the Horn • Writing on the Web The Spyglass Dispatch is a free newsletter sent
Issue 340 - Elon Musk hints at a new model for large families
Thursday, November 21, 2024
View this email in your browser If you are just now finding out about Tesletter, you can subscribe here! If you already know Tesletter and want to support us, check out our Patreon page Issue 340 -
Data Science Weekly - Issue 574
Thursday, November 21, 2024
Curated news, articles and jobs related to Data Science, AI, & Machine Learning ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Programmer Weekly - Issue 232
Thursday, November 21, 2024
View this email in your browser Programmer Weekly Welcome to issue 232 of Programmer Weekly. Let's get straight to the links this week. Quote of the Week "Writing software is a very intense,
Better - An AI Powered Code Reviewer
Thursday, November 21, 2024
Top Tech Content sent at Noon! How the world collects web data Read this email in your browser How are you, @newsletterest1? 🪐 What's happening in tech today, November 21, 2024? The HackerNoon
Python Weekly - Issue 677
Thursday, November 21, 2024
View this email in your browser Python Weekly Welcome to issue 677 of Python Weekly. Let's get straight to the links this week. From Our Sponsor Get Your Weekly Dose of Programming A weekly
Web Tools #592 - JS Libraries, Git/CLI Tools, Media/SVG
Thursday, November 21, 2024
WEB VERSION Issue #592 • November 21, 2024 Advertisement Deploy AMD Instinct™ MI300X on Vultr AMD Instinct MI300X accelerators are now available on the Vultr cloud platform. With thousands of AMD
Stop Using the Wrong State Management in Jetpack Compose
Thursday, November 21, 2024
View in browser 🔖 Articles Benchmark Insights: Direct State Propagation vs. Lambda-based State in Jetpack Compose Here, we'll dive into some benchmark analysis on the state propagation approach in
wpmail.me issue#694
Thursday, November 21, 2024
wpMail.me wpmail.me issue#694 - The weekly WordPress newsletter. No spam, no nonsense. - November 21, 2024 Is this email not displaying correctly? View it in your browser. News & Articles State of