For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

1. Go to your applications. Create a new one, and find the values in the Consumer Key and Consumer Secret fields.

2. Use OAuth client information to produce an OAuth 2 access token:

   curl -i --user <consumer_key>:<consumer_secret> -X POST https://api.twitter.com/oauth2/token -d "grant_type=client_credentials"
   
   {"access_token":"<oauth2_token>","token_type":"bearer"}% 
   

Credits:

• https://eladnava.com/deploy-a-highly-available-mongodb-replica-set-on-aws/
• http://www.serverlab.ca/tutorials/linux/database-servers/how-to-create-mongodb-replication-clusters/

Big thanks to Elad Nava and Shane Rainville for writing the above articles that allow me to conduct this guide. If by all means that I violated original post's copyright, please contact me.

Disclaimer