09 March 2011

Enter MongoDB

In order to display exception details quickly, we decided to make use of MongoDB, removing temporary file system and S3 storage alltogether. When an exception hits our API, we do the same processing we’ve always done but store it in a MongoDB collection instead. The three main advantages to you are:

  • Error details are always available, immediately after we receive them. Therefore you can click on the error URL that you receive on the notification emails and start seeing details for the error with no delay.
  • A more robust storage approach, where app instance failures will never cause details to be completely lost. With careful planning, disk space is not an issue either.
  • Better response times: A nice by-product of this change has been that both storing and reading the data has improved the response time of the application by roughly 30%.

via Hoptoad, the cloud, and the pond ahead.

blog comments powered by Disqus