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 have been develop API using asp.net with C# back-end code.
i would like to understand more concept how to make the API support more client to call,
It’s because i want to have experience the same that able to like twitter.
Do you guys have any article like,
how to make the API able to handle concurrency request.
what kind of server that support at least 100 million request / hrs.
Is there any limitation that .Net able to request concurrency per second?
Regards,
Herman
You should look to build a horizontally scalable solution in order to handle large traffic volumes using web farms. Hosting providers like Amazon/Rackspace/Azure offer great Cloud based infrastructures for doing this if you don’t want to concern yourself with the effort and expensive of building your own farm.
There’s some useful information here about general scaling considerations.
Obviously this is not an alternative to optimising your code, and there are also many considerations when building sites to support concurrently before you scale, including correct use of double-checked locking where appropriate and implementing sensible caching based on your requirements. This will go a long way to supporting many requests, particularly if the content is static.