Why Your .NET Monolith Probably Should Not Become Microservices
The migration pattern everyone reaches for, and why it solves the wrong problem in nine out of ten enterprise codebases. What to do instead.
Architecture observations, engineering lessons, and opinions on enterprise .NET systems. Written from production experience, not conference slides.
The migration pattern everyone reaches for, and why it solves the wrong problem in nine out of ten enterprise codebases. What to do instead.
Blocking rarely shows up in development. It shows up at 9am on a Monday when the overnight batch hasn't finished and the business day has started anyway.
The pattern is well-documented and widely adopted. The mistakes teams make with it are just as consistent.
Architecture reviews, codebase audits, and modernisation strategies are a core part of what we do.
Start a Conversation