Home/ Questions/Q 4253034
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T04:53:35+00:00

This may be a very old, many times asked question. But I am not

  • 0

This may be a very old, many times asked question. But I am not able to find a proper answer to it, so asking again.

For the database connections, we always use a singleton object. When the database is being accessed by thousands of users, how does the performance is maintained? I mean if there are thousands of requests per second, how the database connection is managed since we are using a singleton? Are the database requests serialized? Or a singleton is not used in these cases?

I know it is a kind of dumb question, but I am seriously confused. If anyone can give some reference reading link, it will be nice.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not sure whether you’ve confused the use of a plain singleton with a service locator. Both of them are design patterns. The service locator pattern is used by applications to ensure that there is a single class entrusted with the responsibility of obtaining and providing access to databases, files, JMS queues, etc.

    Most service locators are implemented as singletons, since there is no need for multiple service locators to do the same job. Besides, it is useful to cache information obtained from the first lookup that can be later used by other clients of the service locator.

    By the way, the argument about

    “it’s to ensure that there is always only one active connection to your DB”

    is false and misleading. It is quite possible that the connection can be closed/reclaimed if left inactive for quite a long period of time. So caching a connection to the database is frowned upon. There is one deviation from this argument; “re-using” the connection obtained from the connection pool is encouraged as long as you do so with the same context, i.e. within the same HTTP request, or user request (whichever is applicable). This done obviously, from the point of view of performance, since establishing new connections can prove to be an expensive operation.

    • 0