The controller was never the unit. The use case is.
A fat ASP.NET controller refactored one complaint at a time: feature folders, one class per use case, errors as values, and rules that survive leaving HTTP.
#architecture
2 posts · all tags
2 posts · all tags
A fat ASP.NET controller refactored one complaint at a time: feature folders, one class per use case, errors as values, and rules that survive leaving HTTP.
Cache, fan-out, job coordination, leader election, idempotency: running all of it on the one PostgreSQL you already operate, and why SKIP LOCKED is the one pattern deliberately avoided.