Thomas V.

3 minute read

We’ve been using MongoDB in production at AJJ, Inc. for almost two years now. We initially chose Mongo because we needed to store large SOAP responses (500kb/ea on average) and we were in need of a way to cache them locally. Everything worked well, and I had no complaints or gripes unlike many others. Everything was going great until last Friday when the application lost database connectivity. After logging into our Mongo server the problem was immediately apparent: