There might not be single answer to this question, since this is more related to experiences than opinions. The question here is, how should we handle large number of requests for a service? When I say a large number, I mean a number beyond threshold for that service. And just to let you know, I work in spring context deployed inside tomcat server, although framework doesn't matter here. Let's say, I have a service which is deployed in the same context with other services. The threshold defined for this service is 1000 requests per minute (single request can take max 20 seconds), beyond which it might hamper other services in the same context and eventually server health.The one way to control the impact of this service on other critical services could be deploying it in a different context. But different context means, different url of the service or within same url/server, deploying different contexts sharing same server context parameters.Need to understand real-life experiences on this scenario, as what are the different ways to handle such case.
Handling large number of API requests
java;api;http;spring