Hacker News Reader

Comment by threeseed | Hacker News Reader

Will be great if PostgreSQL ends up as a storage engine option in MongoDB like InnoDB. Then you have the better engine of PostgreSQL with the superior clustering, sharding and end user experience of MongoDB.

That said these articles are pretty pointless. Performance isn't the reason companies are switching to MongoDB.

View on HN

How about implementing MongoDB API on top of the PostgreSQL? Then sell it companies which started with MongoDB, but run into some scalability/reliability issues.

As sad as it may be, with the use of schema-enforcing ORMs and the popularity of MongoDB, this will be a viable business in the near future.

Pretty sure it's easier to add PostgreSQL as a storage engine:

http://engineering.objectrocket.com/2014/07/18/experimental-...

Than to fix up the sharding and clustering in PostgreSQL. It's been an issue for quite a few years now and still not mainlined. I think most PostgreSQL users are simply scaling them vertically.

Someone's already done a proof of concept of this, see https://github.com/JerrySievert/mongolike

This is the thing I was actually thinking of when I posted the above. This is a background worker (runs within PostgreSQL) speaking the mongo wire protocol: https://github.com/umitanuki/mongres

Again, very basic PoC.

I wonder how far one could go with this. I'm currently playing around with Meteor which requires MongoDB. I wonder if a MongoDB API on top of PostresSQL would be a path to start bringing in relational DB capabilities to Meteor? But perhaps Meteor's use of Mongo is too deeply intertwined and goes deeper than an application-level API.

Metor contains an implementation of mongodb written in js to support transparent use of data access in eith client or server.

IBM already does this with DB2 http://www.theregister.co.uk/2013/06/05/ibm_db2_mongodb/

Got a friend recently who used mongodb as first choice for an easy db. He got crazy, dropped it after a month, recoded the thing for postgres in 2 weeks and its been working ever since.. and hes now another die hard postgres fan.

Sooo I don't know.

Are you confusing MySQL and MongoDB? InnoDB is a MySQL storage engine.

threeseed probably wants to use Postgres as a robust transactional backend for MongoDB much like InnoDB is used as a robust transactional engine for MySQL. (There is TokuMX that might fit that use case also).

The idea is that postgres would be a storage engine for mongodb, like innodb is a storage engine for mysql

I don't think MongoDB would have much left to do, if PostgreSQL was doing the storage duties. The converse - implementing the MongoDB protocol within PostgreSQL, as mentioned above (mongolike), sounds like a more sensible proposal.

Reply on news.ycombinator.com