Backend engineering
Architecture and delivery work on a distributed platform of ASP.NET Core APIs. The platform uses Domain-Driven Design and Vertical Slice Architecture to organise business capabilities and isolate responsibilities.

Conceptual workflow diagram showing service boundaries, owned SQL data, and Azure Service Bus
The problem
Large application domains need service boundaries that support growth without tightly coupling every feature and integration.
The approach
Organise services around business domains and vertical feature slices, using messaging for service communication and containerisation for delivery. Document API contracts through OpenAPI.
- Domain-oriented service boundaries
- Vertical feature slices
- Azure Service Bus integration
- Containerised APIs with OpenAPI documentation
My contribution
Backend architecture & API development
Technology
ASP.NET Core, .NET 8 / .NET 9, EF Core, SQL Server, Azure Service Bus, Docker, OpenAPI
Discuss a similar workflow