Every internal API eventually grows an export endpoint, and it is almost always the same story. Somebody in finance asks for "the transactions as a spreadsheet", a developer adds GET /transactions/exp
The browser console message is always some version of this: Access to fetch at 'https://api.example.com/orders' from origin 'https://app.example.com' has been blocked by CORS policy: No 'Access-Contro
Minimal APIs are genuinely good now. The performance is excellent, the tooling caught up, and on .NET 10 the last few gaps that used to justify reaching for controllers have closed. What has not chang
You upgraded a service, deployed it, and a single endpoint started throwing this: System.InvalidOperationException: Synchronous operations are disallowed. Call ReadAsync or set AllowSynchronousIO to t
For years the honest advice on how to migrate Newtonsoft.Json to System.Text.Json in ASP.NET Core was "wait". Two features kept teams pinned to AddNewtonsoftJson(): JSON Patch and polymorphic serializ
The first AI endpoint I put behind a rate limiter was protected by a policy that allowed 60 requests per minute per user. It felt responsible. Two weeks later one customer generated a bill larger than
