Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am designing a typical ASP.NET site which will connect to database to retrieve and display data. Its a three tier logical implementation with database, middle and presentation layer.
Should the class which creates a connection to the database be implemented as singleton ?
Does it mean that there will be always only one connection to the database ?
I have heard of connection pooling in ASP.NET. Isn’t by making it singleton, we are ignoring this feature of ASP.NET ?
No. Let me be the first to say that the Database Connection shouldn’t be a Singleton.
Instead, investigate the Unit of Work pattern. Each Unit of Work should have its own connection to the database.