Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
It turned out to be a versioning issue with my production droplet. The droplet was running nodejs and mongodb that was coming from the ubtuntu repository hosted by digital ocean. The restriction was possibly coming from running older versions and I was not able to figure out how to apt-get newer versions from the Trusty Trah repository hosted by digitalocean.
Upon updating to NodeJS v4.0.0 and MongoDB v3.0.6 on my Ubuntu server, I was able to see my GET request now returning 7771 records as expected.
After a apt-get remove and purge of “mongodb” and “nodejs”, I ran the following to install NodeJS v4.1.2:
curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs
Next, I followed this guide to install mongodb 3.0.6 http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/
This fixed all the limit issues I was having in the app.