Software Architect specializing in cloud-native systems, distributed systems, integration architecture, and practical software engineering.
18+ years designing and building software systems. Azure is my primary platform. I help teams turn business problems into systems that are simple to understand, safe to change, and easy to own.
This profile is where I share that work — the systems I build, the engineering behind them, and the decisions that shape them.
If you'd like to know more about my background and how I approach architecture, visit my About page.
If you're here to explore my work, these are the best places to start:
Practical Azure integration architecture through working .NET examples, messaging, APIs, event-driven systems, resilience, and architectural trade-offs.
→ Azure Integration Architecture
Deeper explorations of architecture patterns and distributed systems — building the solution, testing it, breaking it, documenting the decisions, and explaining what I learned.
→ Architecture Through Engineering
The blog is where I explain the architectural reasoning, trade-offs, experiments, and lessons behind the engineering work.
For practical implementation examples, take a look at:
- Wire Tap Middleware — Azure Service Bus middleware and messaging
- Business before technology.
- Architecture through engineering.
- Simple systems age better than clever ones.
- Documentation belongs with the code.
- Every architectural decision is a trade-off.
- Learning never stops.
- Cloud-native and distributed systems architecture
- Integration architecture and event-driven design
- API and platform design for systems built to last
- Practical software architecture through hands-on engineering
"Architecture isn't the goal. Helping people make better decisions is."