Blog

Page 5 of 6

C4 Model: Architecture Maps That Actually Help
Documentation

C4 Model: Architecture Maps That Actually Help

The C4 model gives architecture diagrams four levels of zoom, from context down to code. Here is what each level shows and who actually needs to see it.

7 min read
When Systems Talk Without Knowing Each Other: Pub-Sub
Design PatternsIntegration

When Systems Talk Without Knowing Each Other: Pub-Sub

Pub-sub architecture lets systems react to the same event without knowing each other. The benefits, when to use it, and lessons from a retail loyalty platform.

8 min read
Health Endpoints: When Production Sleeps with One Eye Open
ObservabilityResilience

Health Endpoints: When Production Sleeps with One Eye Open

Health endpoints tell you in one request whether a service is alive, its dependencies are reachable, and it can take traffic. How to build ones you can trust.

6 min read
How to Stop One Service from Burning Down the House
Design PatternsResilience

How to Stop One Service from Burning Down the House

The circuit breaker pattern stops one failing dependency from turning into a retry storm that takes down your platform. A real payment outage, fixed with Polly.

8 min read
The BFF Pattern: Friendship Goals for Frontend and Backend
Design PatternsAPI Design

The BFF Pattern: Friendship Goals for Frontend and Backend

The BFF pattern gives each frontend its own backend, so mobile, web and TV stop fighting over one shared API. When to use it, and when it is just overhead.

7 min read
The Gentle Art of Strangling Legacy Systems Without Breaking Everything
Design PatternsModernization

The Gentle Art of Strangling Legacy Systems Without Breaking Everything

The strangler fig pattern replaces a legacy system piece by piece behind a facade, so you avoid a risky full rewrite. Lessons from replacing a 15-year-old CRM.

5 min read
The Ambassador Pattern: Because APIs Have Bad Days Too
Design PatternsResilience

The Ambassador Pattern: Because APIs Have Bad Days Too

The ambassador pattern puts a sidecar proxy in front of the APIs your service calls, so retries, timeouts and logging leave your service code. Shown with Envoy.

7 min read
Conway’s Curse: When Your Org Chart Haunts Your Codebase
Organizational Design

Conway’s Curse: When Your Org Chart Haunts Your Codebase

Conway's Law means you ship your org chart. Why it still shapes your microservices, and how the inverse Conway manoeuvre lets you design teams and code as one.

6 min read
Architecture Fitness Functions: Catch Drift Before Prod
Quality & TestingArchitecture Practices

Architecture Fitness Functions: Catch Drift Before Prod

Architecture fitness functions turn qualities like latency, security, and modularity into automated checks that catch drift in CI/CD before it hits production.

6 min read