Should I Use One DbContext Per HTTP Request in My Application?

DBContext Best Practice: Each HTTP request a DBContext

In the ASP.NET CORE application, the creation of a new DBContext instance for each HTTP request is widely recommended. The reason is as follows:

Avoid data cache problems and performance improvement

DBContext can cache the data. If multiple requests access the same data at the same time, the data may be expired. DBContext using a single mode will limit the data cache to the scope of a single request, reduce the database calling, thereby improving performance.

The advantage of each request a DBContext

Single business affairs: Multiple operations are executed in a DBContext to facilitate transaction processing and ensure data integrity.

Simplified code:
• The class that modifys the data only needs to call , reduce the complexity of the code, and avoid the responsibility of managing DBCONTEXT.
Entity sharing:
• The entity can easily pass within the request range, because they all come from the same DBContext. _context.SaveChanges() The disadvantages of the transient DBContext
• Although it is feasible to register DBContext as a transient service, it may lead to the following problems:

Manual change tracking:

Each object must call to save changes, increase complexity, and violate the principle of single responsibilities.

Entity scope limit:

The entity cannot leave the scope of the class that loaded them, and cannot be used in other classes.

Release Management:
• Correctly release the DBCONTEXT instance requires an additional domain mechanism or manual processing. context.SaveChanges() Other optional solutions
• Use DBContextFactory for explicit control:
Inject DBCONTEXTFACTORY to allow business logic to explicitly control the creation and release of DBContext to provide greater flexibility.
• The unit of container management: Let the DI container manage DBCONTEXT, maintain the business logic simple, and abstract the creation, release and submitting process.

Affairs decorations:

The decorative device can be applied to the command processing program to ensure the correct transaction management and submit it only when successful.

The above is the detailed content of Should I Use One DbContext Per HTTP Request in My Application?. For more information, please follow other related articles on the PHP Chinese website!