I'm having doubts about a need to use a singleton pattern in a web service.
I'm building a web service that is acting as a server side for multiple clients. I was thinking about making my business logic classes a singleton classes but i'm having doubts because of the following scenario:
When the web service receives calls from multiple clients simultaneously to invoke the same method,i assume that they all have to wait in a queue because there is only one business logic instance.
On the other hand, having the same scenario without using a singleton will cause multiple business logic instances, one instance for each client.
I would love to receive a recommendation or a best practice for my scenario.