Treat your .NET Minimal API Endpoint as the application layer about timdeschryver.dev HOT 1 CLOSED

I think there's something to be said for at least considering a single layer of abstraction of the data access. The last project I worked on, we wrote a Web API as a mono-project monolith. Then when we needed to build a scheduled job (running as a container in AWS) that used parts of the same data access patterns, we simply created another very thin console project host and re-used the same Repository classes that the Controllers in the Web API runtime were using.

The risk with direct DbContext access is ending up with multiple implementations of more complex data access patterns. A UnitOfWork or Repository implemented in the same project (to reduce build complexity and build time) seems like a good compromise.

from timdeschryver.dev.