Microservices rules #10: Make smaller, safer, and reversible changes - part 3
This is the fifth article in the series about microservices rules: what good looks like, which are a set of
Visualizing technical debt using quality views
Previously, I wrote about how to build a business case for reducing technical debt including the importance of making the
Microservices rules #10: Make smaller, safer, and reversible changes - part 2
This is the fourth article in the series about microservices rules: what good looks like, which are a set of
Building a business case for reducing technical debt
As far as I can tell, most organizations are drowning in a technical debt.
This is a major problem because
Microservices rules #10: Make smaller, safer, and reversible changes - part 1
This is the third article in the series about microservices rules: what good looks like, which are a set of
Evolving an architecture: a problem solving-driven approach
Over the years, I’ve been asked repeatedly about the granularity of services in a microservice architecture.
I used to
Microservices rules #5: Deliberative design
This is the second article in the series about microservices rules: what good looks like, which are a set of
Doing more with less: Part 4 - making sure that buying is really better than building
This is the fourth article in a series of articles that describe how engineering leaders can do more with less
There’s more to a microservice architecture than services
From time to time, I encounter organizations who have been struggling with their microservice architecture.
Sometimes, the problem is data
Doing more with less: Part 3 - Buy don't build using Wardley Mapping
This is the third article in a series of articles that describe how engineering leaders can do more with less
