A proof of concept MongoDB clone built on Postgres

I suspect there are lots of people who built applications on top of MongoDB who would like to transition away from Mongo onto a different database, or would at least like the option to be able to to. This may provide a good mechanism for a transition.

Which leads to a question for the OP: does this work with mongoose.js?

Re: A proof of concept MongoDB clone built on Postgres

#5

Post by bryanlarsen » Mon, Apr 20, 2015, 12:31 PM UTC

At the bottom of the README it says "Follow along at http://legitimatesounding.com/blog/", which 404's. I want to follow along! Please fix. Thanks.

Re: A proof of concept MongoDB clone built on Postgres

#6

Post by nl » Mon, Apr 20, 2015, 12:33 PM UTC

How are JSON updates handled?

For those who aren't aware, Postgres currently lacks support for doing updates to JSON fields via SQL[1]. For many this isn't a problem, but I'd imagine that people expecting a MongoDB clone would need it.

[1] But even though you can individually address the various fields within the JSON document, you can’t update a single field. Well, actually you can, but by extracting the entire JSON document out, appending the new values and writing it back, letting the JSON parser sort out the duplicates. https://blog.compose.io/is-postgresql-your-next-json-databas...

Re: A proof of concept MongoDB clone built on Postgres

#7

Post by tinco » Mon, Apr 20, 2015, 12:34 PM UTC

I was going to post that this would have been cool a year ago, but now that MongoDB has interchangeable backends there's not much to gain from a high level project like this.

But then I saw that this project started two years ago, and the last commit was a year ago.

Re: A proof of concept MongoDB clone built on Postgres

#8

Post by worldsayshi » Mon, Apr 20, 2015, 12:48 PM UTC

tinco wrote: post #7

I was going to post that this would have been cool a year ago, but now that MongoDB has interchangeable backends there's not much to gain from a high level project like this. But then I saw that this project started two years ago, and the last commit was a year ago.

| MongoDB has interchangeable backends

Do you have a source on this? I can't find anything at the moment but it sounds familiar.

Re: A proof of concept MongoDB clone built on Postgres

#9

Post by bryanlarsen » Mon, Apr 20, 2015, 12:52 PM UTC

worldsayshi wrote: post #8

tinco wrote: post #7

I was going to post that this would have been cool a year ago, but now that MongoDB has interchangeable backends there's not much to gain from a high level project like this. But then I saw that this project started two years ago, and the last commit was a year ago.

| MongoDB has interchangeable backends Do you have a source on this? I can't find anything at the moment but it sounds familiar.

The feature is called "pluggable storage engine", if you want something to Google.

Re: A proof of concept MongoDB clone built on Postgres

#10

Post by benlambt » Mon, Apr 20, 2015, 12:58 PM UTC

nl wrote: post #6

How are JSON updates handled? For those who aren't aware, Postgres currently lacks support for doing updates to JSON fields via SQL[1]. For many this isn't a problem, but I'd imagine that people expecting a MongoDB clone would need it. [1] But even though you can individually address the various fields within the JSON document, you can’t update a single field. Well, actually you can, but by extracting the entire JSON…

Write a function in PLV8?