Why should you care?

Starting with folders and boundaries prevents User logic from leaking into Order.Api later.

See it live — copy this example

Create a Web API project (dotnet new webapi), paste the code, then run dotnet run.

ShopNest.User/
  src/User.Api/
  src/User.Application/
  src/User.Domain/
  src/User.Infrastructure/
  tests/User.UnitTests/

Run Example »

This lesson uses terminal or setup steps. Run commands on your computer — the live editor appears on coding lessons.

What happened?

• Api references Application; Application references Domain; Infrastructure references Application contracts.
• Domain has zero references to EF or ASP.NET.

Try it yourself

1. mkdir ShopNest.User && cd ShopNest.User
2. dotnet new sln -n ShopNest.User
3. dotnet new classlib -n User.Domain && dotnet new classlib -n User.Application
4. Change a string or route in the example and save — watch Swagger or the RabbitMQ Management UI update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

User service = separate solution. Four layers from day one. Domain has no infrastructure dependencies.