4 ms·
I wish I could upvote this comment more. I have to run over a hundred instances of MongoDB to equal the performance I could get from ten Postgres boxes, but no
by nasalgoat 13y ago
I wish I could upvote this comment more. I have to run over a hundred instances of MongoDB to equal the performance I could get from ten Postgres boxes, but now we have such massive lock-in on MongoDB we can't easily refactor.
- jeltz 13y agoWould it be possible for you to write a wrapper and use the Mongo API against another DB?
- nasalgoat 13y agoThe main issue is it being a JSON document store, and our application being designed around that and using the very specific MongoDB queries that involves. Any wrapper would likely be worse than just keeping MongoDB.
- Two9A 13y agoHeh, do you work at my place? We have the exact same issues with Mongo-specific queries. Even worse, our indexing regime (because we store relational data in Mongo) demands that we stick with Mongo 1.8, so all the comparative goodness of 2.x is lost. And just this week, it was determined that there won't be any migration from Mongo to something-SQL in the near future, because it'd be too risky to attempt to translate a schema that's half foreign keys, half embedded JSON.
- gazarsgo 13y agoCan't you just jam the data into Postgres JSON columns? :)
- gaius 13y agoYes http://www.ibm.com/developerworks/data/library/techarticle/dm-1306nosqlforjson1/index.html?ca=drs- http://www.ibm.com/developerworks/data/library/techarticle/d...