Why Does Microsoft Advocate Asynchronous Calls in its EF 6 ASP.NET MVC 5 Tutorial?

Microsoft's EF 6 ASP.NET MVC 5 Tutorial: The Case for Asynchronous Database Calls

The latest EF 6 tutorial for ASP.NET MVC 5 strongly promotes asynchronous database access, exemplified by code like:

<code>Department department = await db.Departments.FindAsync(id);</code>

Let's weigh the pros and cons of asynchronous versus synchronous approaches:

Asynchronous Advantages:

• Reduced thread pool exhaustion.
• Increased concurrency.
• Lower memory consumption.
• Intra-request concurrency support.
• Potential performance gains under heavy load.

Synchronous Advantages:

• Simpler code structure.
• Less development and debugging overhead.
• Better profiler compatibility.
• Easier integration with existing code.

When to Choose Asynchronous:

Microsoft advises using asynchronous calls in ASP.NET applications when interacting with high-latency services, such as web services and lengthy database operations. For low-latency operations (database or file system access), synchronous calls are usually more efficient.

Reasons Behind Microsoft's Recommendation:

The EF team's emphasis on asynchronous programming might stem from:

• Internal company guidelines.
• Anticipation of EF use in client-side applications.
• A potential overestimation of the benefits for database calls, overlooking potential drawbacks.

It's crucial to remember that asynchronous calls should only be implemented when they provide substantial advantages. Mixing synchronous and asynchronous patterns within a single application is perfectly acceptable.

The above is the detailed content of Why Does Microsoft Advocate Asynchronous Calls in its EF 6 ASP.NET MVC 5 Tutorial?. For more information, please follow other related articles on the PHP Chinese website!