Scaling MongoDB on OpenShift vs using MongoLab [closed]

StackOverflow https://stackoverflow.com/questions/22692520

Question

Coming from a "traditional" development background, I cringe whenever I see PaaS NoSQL offerings. The idea of hosting your data far from your application simply does not feel right. But PaaS providers like MongoLab are here and are seemingly very successful.. so I think to myself, it must be working.. I should consider it.

I'm building an application using NodeJS and MongoDB and will be hosting it on OpenShift. Ideally, I have both Web Servers and a Mongo cluster setup that I can easily scale them horizontally... all hosted on OpenShift.

Does it make sense to host/scale Mongo on OpenShift? Should I go with a PaaS like MongoLabs?

UPDATE: I'm asking about the architectural reasons why one chose to host data away from your app in a PaaS-type offering vs hosting it yourself in a service like OpenShift. The specific services I'm listing here are irrelevant as it could apply to other hosting service, NoSQL database, or PaaS provider.

Was it helpful?

Solution

MongoLab is actually a DBaaS (DataBase as a Service) not a PaaS, just for clarification.

The reasons for hosting a database etc offsite is similar to hosting files offsite with say Amazon S3. You are looking for a service that specializes in what you are using it for. MongoLab specializes in MongoDB, sharding, replication, large data sets etc. They would be a great provider if you need those services. If not, then the MongoDB instance on OpenShift should be fine, you can even use a scaled application to get into it's own gear, but we do not support sharding or replication for MongoDB at this time.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top