Smartphones and tablets have dramatically shifted the way we consume—and create—digital content. Information is instant. The length of time it takes web-based companies to attract a million users has sharply decreased for modern apps that catch the public’s imagination. What once took several months–even years–now takes just weeks.
In yesterday’s post I considered some of the limitations of running MongoDB on the public cloud. In the event that you decide to host MongoDB with a cloud provider, below are some thoughts on how to choose the right one. The framework is actually applicable to many other data services, but we will continue to use MongoDB for the discussion.
It wasn’t too long ago that developers and database administrators answered with a simple “no, thank you” when asked about implementing any database on virtualized or cloud environments. The state of database-as-a-service solutions has come a long way in a relatively short period of time. Today, the number of choices available to developers in the data services tier has exploded.
This is a guest post written and submitted by Greg Avola, CTO, Co-Founder and Developer at Untappd, an ObjectRocket customer. Untappd is a mobile app that allows you to socially share the brew you’re currently enjoying, as well as where you’re enjoying it, with your friends.
I started writing small web applications in the late 90s. I came from a traditional relational database background, relying heavily on one of the most popular open source solutions, MySQL. After seeing a lot of online discussion around non-relational databases, and having talked to a number of customers looking for help with MongoDB, I knew that it was time to learn something new and get my feet wet with non-relational databases. Here are some of the steps I took and resources I used to learn MongoDB.