Managing Database Connections in ASP.Net MVC

Question

I am new to ASP.Net MVC and I have written a number of Controller classes that have this ivar:

private ApplicationDbContext db = new ApplicationDbContext();

I have also read that each request creates a new instance of the Controller.

I am concerned about database connection churn.

Should I be using a single global connection object instead? Or is there connection pooling happening behind the scenes and I shouldn't worry about it?

Felipe Oriani · Accepted Answer · 2015-06-29 22:00:35Z

1

For Entity Framework ORM tool, it is not recommended to use DbContext as a singleton instance, so, avoid to keep it on the global.asax. A good pratice is to use it with the pattern Unit of Work. Read this article.

In this another article you can see sample pros and cons about how to keep an instance of DbContext.

answered Jun 29, 2015 at 22:00

Felipe Oriani

38.7k20 gold badges141 silver badges203 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Managing Database Connections in ASP.Net MVC

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related