The user wants me to rewrite a headline about synchronous vs asynchronous in .NET Core.

Short summary

Async/await in .NET Core: use async for I/O-bound work (database calls, HTTP requests, file I/O) to free request threads and handle more concurrent requests with the same thread pool. Keep synchronous for trivial, instant CPU work; for expensive CPU operations, offload to background workers—async alone won't improve CPU performance. Always propagate CancellationToken end-to-end and never block on Task.Result or .Wait(), which can cause deadlocks and thread-pool starvation.

• •Use async for I/O-bound operations (DB, HTTP, files) to free threads; keep trivial CPU work synchronous
• •For heavy CPU tasks, offload to background workers instead of just wrapping with async
• •Propagate CancellationToken end-to-end and avoid blocking on Task.Result/.Wait() to prevent deadlocks

Generated with AI, which can make mistakes.