Microservices rules #7: Design loosely design-time coupled services - part 1
This is another article in the series about microservices rules: what good looks like, which are a set of principles
Office hours - Tuesday March 11th, PDT
Hi,
There will be two office hours sessions for paid subscribers on Tuesday March 11th, Pacific Daylight time
See below
Microservices rules #10: Make smaller, safer, and reversible changes - part 5
This is another article in the series about microservices rules: what good looks like, which are a set of principles
Microservices rules #11: Track and improve metrics
This is another article in the series about microservices rules: what good looks like, which are a set of principles
Microservices rules #3: Apply Team Topologies
This is another article in the series about microservices rules: what good looks like, which are a set of principles
Microservices rules #1: Practice continuous delivery
This is another article series about microservices rules: what good looks like, which are a set of principles and practices
The progress principle: the key to improving productivity and job satisfaction
Today, there’s growing interest in improving the Developer Experience (DevEx).
And, for good reason: a great developer experience increases
Microservices rules #10: Make smaller, safer, and reversible changes - part 4
This is the sixth article in the series about microservices rules: what good looks like, which are a set of
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
