I will build dotnet microservices with rabbitmq


About this gig
Need two systems that talk through events instead of direct calls? I build event-driven .NET microservices with RabbitMQ and SQL Server.
Based on OrderFlow, my own project: an Orders service and an Inventory service, each with its own database. When an order is created, Inventory checks the stock and replies with an event, and Orders confirms or rejects it.
PACKAGES
- Basic: two .NET services, each with its own SQL Server database, connected by one RabbitMQ event
- Standard: Basic + full order flow (stock check, confirm or reject) and Docker Compose
- Premium: Standard + one extra event or service adapted to your business case
ALL PACKAGES
ASP.NET Core (.NET 9), EF Core, source code and a README with setup steps.
WHAT I NEED
Your business flow (orders, bookings, payments...) and the events your services should exchange. Basic and Standard use the OrderFlow flow; adapting it to your case is Premium.
NOT INCLUDED
UI, authentication, hosting, and advanced reliability (retries, dead-letter queues, outbox) unless agreed beforehand.
Not sure which package fits? Message me before ordering.
Get to know Lucas Aguilera
Software Development Technician
- FromArgentina
- Member sinceAug 2026
- Avg. response time2 hours
Languages
English
My Portfolio
FAQ
Do the services run on my own machine?
Yes. You receive the source code and a README. RabbitMQ and SQL Server start with Docker Compose, and each service runs with dotnet run.
Can you adapt this to my own business case?
Yes, that's what the Premium package is for. Message me before ordering so we can check that it fits.
Do you include a user interface or authentication?
No. This gig covers the backend services and the event flow only. If you need authentication, message me first and we'll agree it as a custom offer.
Which technologies do you use?
.NET 9, ASP.NET Core, Entity Framework Core, SQL Server and RabbitMQ, with Docker Compose for the infrastructure.
What happens if one service is down?
The events stay in the RabbitMQ queue and are processed once the service starts again, so no message is lost.

