Hacker News Reader

Comment by jakozaur | Hacker News Reader

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.

View on HN

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.

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.

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/

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.

Reply on news.ycombinator.com