New premium article: a service exists to solve problems
architecting microservice architectureContact me for information about consulting and training at your company.
The MEAP for Microservices Patterns 2nd edition is now available
Until July 25th, enroll for $95 in my virtual bootcamp, distributed data patterns in a microservice architecture
I’ve written a new article for premium subscribers, a service exists to solve problems This article is follow up to my previous article, Thoughts about service granularity. It digs deeper into the idea that a service should only be added to an architecture if it solves a problem. I explore the idea that an architecture is the result of a series of design decisions, each of which solves a problem and modifies the architecture by adding, removing or modifying architecture elements. Consequently, you should be able to trace each service back to a design decision and the problem that it was intended to solve.