01Architecture
Why Microservices Fail When Service Boundaries Are Wrong
A service boundary is a decision about ownership and change, not a way to divide a codebase into smaller deployments.
Blog
Engineering Notes
Practical thinking about backend architecture, identity and the places where production systems become difficult. Concepts and design guidance, without invented incident stories.
02Identity
Debugging OAuth 2.0 and PKCE in SPAs
Follow the authorization-code flow one boundary at a time, and distinguish the browser, identity provider and API responsibilities.
03Security
Designing API Scopes in a Microservices Architecture
Scopes describe delegated access. They are one part of authorization, not a replacement for resource-level rules.
04Messaging
RabbitMQ vs Synchronous Service Communication
Choose communication by consistency, failure behavior and who needs an answer now.
05.NET
Building a Production .NET Microservices Environment with Docker
A container image is one part of a production environment. Configuration, identity and operational behavior complete the picture.
06Troubleshooting
Debugging TLS, DNS and Reverse Proxy Problems
Follow the request in order. A failure at one layer can look like an application bug at another.
07DDD
Why Product Services Should Avoid Direct Dependencies on Seller Databases
Convenient database access can quietly make one service’s internal schema another service’s contract.
08Read Models
SupplierReadModel: Keeping Microservices Decoupled
A local projection gives Product the seller information it needs without sharing database ownership.
Contact
Have a difficult .NET problem?
Need help with a microservices architecture, production issue, authentication problem, or distributed system?