I design and build event-driven backends in .NET, where independent services communicate through RabbitMQ instead of direct calls, so one service can fail without taking down the others.

Two independent ASP.NET Core services, each with its own SQL Server database

Asynchronous communication through RabbitMQ events (publish, consume, and result events)

Order flow with stock validation: orders end up confirmed or rejected

Docker Compose setup for SQL Server and RabbitMQ

Clean README with architecture diagram and step-by-step run instructions

Source code on GitHub

Cloud deployment or Kubernetes

Frontend / UI

More than two services (extra services can be quoted separately)

How it works You tell me the flow you need (for example orders and inventory, or any two domains that must stay decoupled). I deliver a working, documented system you can run with one command and extend later.

See my OrderFlow case study for a real example of this architecture.