I will build a dotnet 9 microservice with clean architecture
About this gig
A .NET service built the way it should have been built the first time.
I maintain an open-source clean-architecture foundation for .NET 9 microservices production-grade infrastructure, zero business logic. It is linked from my profile, so you can read the standard you are buying.
In my day job I architect eight .NET 9 microservices in production, each owning its database, talking REST and gRPC.
WHAT YOU GET
A running service with the layers separated and the dependency direction enforced, not hoped for: Domain, Persistence, Application, WebAPI. EF Core 9 with proper entity configuration. FluentValidation on every request. A consistent response envelope so your frontend never guesses. Global exception handling. JWT auth. Swagger. A migration path that will not break on your second deploy.
Handed over with a README explaining how to add the next entity without me.
WHY IT MATTERS
Every .NET project I am asked to rescue died the same way: business logic in controllers, one enormous DbContext, no transaction boundaries, migrations nobody dares run. Getting the skeleton right costs days and saves months.
WORKS WITH
SQL Server, PostgreSQL, MySQL. Docker if you want it.
Get to know Mosfik
Dotnet and Java backends, built to survive the second year
- FromBangladesh
- Member sinceFeb 2022
- Avg. response time1 hour
- Last delivery1 year
Languages
Bengali, English, Hindi
My Portfolio
Other Software Development Services I Offer
FAQ
Can you work with my existing codebase, or is this only for new services?
Both. If you have an existing project I will work inside your conventions rather than impose mine. Send me the repository and I will tell you before you order whether the work fits this gig or needs a custom quote.
Which databases do you support?
SQL Server, PostgreSQL and MySQL out of the box. Others are usually fine, just ask first.
Do you write tests?
Unit tests are included in Premium and available as an extra on the other tiers. I would encourage it: a service with no tests is cheaper once and more expensive every month afterwards.
Will I be able to add features myself afterwards?
That is the point. You get a README explaining how to add the next entity end to end, and the structure is deliberately repetitive so the second one is copy-and-adapt.
Do I own the code? Can I use it commercially?
Yes, fully, on delivery. No licence, no attribution, no strings.
What if my requirements change mid-project?
Tell me early and I will re-scope honestly, either inside the current order if it is small or as an extra if it is not. What I will not do is quietly absorb it and deliver late.
Do you deploy it for me?
A Dockerfile is included in Premium and available as an extra on the other tiers. Deploying to your own cloud account is a separate conversation, message me and I will quote it.
How do we communicate, and how often?
Through Fiverr, with an update every two days minimum. I work GMT+6, which is a full afternoon of overlap with Europe and most of the working day with the Gulf.

