Backend .NET
HTTP services and workers in .NET running in enterprise production: REST APIs, scheduled processing, integration with a heavy relational database and with third-party systems. It is the base of the dozens of systems of which I am the main author.
Day to day that means Entity Framework Core and FluentValidation in most of what I write, with Dapper where the query needs to leave the ORM: a heavy report, a join EF does not handle well, a procedure that already existed before me.
Two live ends at the same time
I have worked from .NET Framework 4.5 to .NET 10. Living with both ends is part of the job, not an exception: the legacy cannot stop while the new comes up, and migrating an application to a new version without breaking compatibility with a shared Oracle schema is a recurring task.
What I do
- Model and expose REST APIs with a versioned contract and a standardized error response
- Write scheduled processing workers, with the schedule declared outside the code
- Choose between ORM and direct SQL case by case, as described in Data and persistence
- Migrate legacy applications to a modern framework version without breaking database compatibility
- Extract what repeats across services into a shared library
- Instrument for observability: structured logs, health checks, integration tracing
- Take care of dependency injection, per-environment configuration and what goes wrong with
async/await(deadlock from synchronous blocking, synchronization context, cancellation)
Where I applied it
Payments and anti-fraud · Commissions · Experience
What I have not done yet
I have not worked with .NET in a very high concurrency scenario with latency requirements in milliseconds. My typical problem is moderate volume with complex integration, not extreme throughput. I also have no production experience with gRPC or Orleans.