Backend .NET for systems that cannot stop
I design and review high-availability APIs, microservices and the architecture behind them. Over 20 years in mission-critical systems, with decisions explained in language that both the team and leadership understand.
Where I can help with your backend
Architecture review
Reading the current system, a risk map and a prioritized evolution plan. Works for legacy .NET and for new systems before they grow.
High-availability APIs
Resilience, idempotency, versioning, observability and error handling designed for real traffic, not just the test environment.
Monolith or microservices
A decision based on your context: team, scale and operational cost. Includes the modular monolith path, when it solves the problem with less complexity.
How I work
1. Understand
Conversations with the people who run the system, reading the code and recent incidents. The starting point is the real problem.
2. Decide
Options with clear trade-offs and a recommendation, recorded as architecture decisions (ADRs) the team can maintain.
3. Deliver
I follow the implementation with code review and .NET examples, so the decision reaches production and does not stay on paper.
Results I have delivered
Digital credit platform, white label platform for 4 global brands and a B2B fleet platform. See the cases on the Professional page.
Want the reasoning behind the decisions? Read Clean Architecture in .NET, Monolith vs Microservices, Modular monolith in .NET and API Gateway and BFF in .NET.
Frequently asked questions
When does it make sense to move from a monolith to microservices?
When team organization or the scale of specific parts of the system no longer fit in a single deployment. Before that, a well-modularized monolith usually costs less and delivers more. The decision comes from a diagnosis of your system, not from a general rule.
Do you work with legacy .NET Framework systems?
Yes. The work starts by understanding what sustains the business today and defining an evolution path in small steps, without stopping operations.
What does a first conversation look like?
A 30-minute call to understand the context, the bottleneck and what you expect. If it makes sense to continue, we agree on the format: architecture review, team support or the design of a specific solution.
Do you also work with AI in development?
Yes. I use Claude Code in the .NET development workflow, with human review and traceability from specification to test. See the articles on the topic on this site.