@simas_ch I usually start out this way, but then as soon as the entity and dto are slightly different I separate them. This happens eventually in most solutions. When this split is done on several endpoints, it makes sense to do it for the whole solution to stay consistent.
@Dave_DotNet Minimal api, mainly because of performance. But also less magic than controllers.
I have one file per endpoint, this includes both the handler and the register method. All endpoints are registered automatically on startup using reflection. Very simple and clean
@Dave_DotNet I changed primary key from v4 to v7 on table with several million rows a SQL database last year. Even tough the existing rows was used v4 id, the perf inprovement on all new inserts using v7 was significant.
@LaylaCodesIt My most important rule is that there should be no EF references outside my infrastructure project. If some entity suddenly needs to be stored in a way that EF does not support it is a pure infrastructure concern and no other part of the code should need changes.
@slace I think you can reduce time to get token if you use a more specified tokencredential, like ManagedIdentityCredential when you know it's managed / running in Azure.
@davidfowl@scottsauber ... that you may have significant overhead in your organization. Alot of places are doing 1 repo per app or deployable. Without even considering why. Often it can make more sense with 1 repo per domain or team. Important to make an informed decision.