It doesn't matter where the WCF service is hosted. It all depends on the binding settings, the endpoint, the behavior of the endpoints and the behavior parameters of the service, and, last but not least, on how you set (through the attributes) the instancing mode and the concurrency type for your service.
These settings are carried over by ServiceHost . Even if it works in a console application, the application itself is just a container for ServiceHost , which creates a runtime for your WCF service based on the settings you give it.
What interests you, see here (concurrency and throttling). In addition, something is very extended in WCF instance modes .
For performance reasons, I recommend that you use a single-user service, which you can specify through InstanceContextMode. If you have hundreds of requests, they will not benefit concurrency if a service instance is created for each request. You should consider whether monotonous use is possible in your case, checking if all of your service operations are thread safe.
source share