1. 36
  1.  

  2. 15

    This guy seems overly emotionally invested in the internals of MongoDB.

    I find Multicorn and UDFs to be excellent extension mechanisms for PostgreSQL. Whatever gets the job done in the least amount of lines. Have

    1. 18

      A quick reading suggests that his company’s complimentary product to MongoDB is being threatened by Mongo’s cheerful repackaging of Postgres–that may have something to do with it.

      1. 13

        I’m the author, and you’re right, I’m definitely not unbiased!

        I have three main biases that I can see: first, I didn’t like the one-sided partner experience I felt at my day job; second, I was a strong proponent for MongoDB to release an Apache 2-licensed BI connector that leveraged open source work I contribute to (which does 100% in-database analytics); and third, I co-founded an open source company based on the premise that relational analytics aren’t a good fit for NoSQL databases.

        So yeah, I’m definitely biased. I try not to let those biases cloud my judgement, but I’m no vulcan.

        I would have a different opinion of the connector if (a) they had been 100% upfront about the Postgres database and the (severe) limitations of the approach, rather than pounding their chest and omitting the Postgres connection; OR (b) they had released their own connector (even proprietary) that properly dealt with the problem (native support for nested data structures, 100% pushdown, etc.).

        They didn’t do either. Which means I can’t get behind their decision. Others may come to very different conclusions, which is fine by me. Agree to disagree. :)

        1. 2

          Gotcha gotcha, good luck to you sir. :)

          Out of curiosity–what do you mean by 100% pushdown?

          1. 5

            Thanks for that! And sorry for the jargon.

            By 100% pushdown, I mean that every query is translated into operations on the target system that run entirely inside the database. Without pushdown, you end up sucking data out of the database, and relocating it into another system which actually executes the query.

            The whole analytics via PostgreSQL via FDW via Multicorn via MongoDB route ends up pulling ALL the data out of ALL the referenced(s) collections for nearly ANY possible query (!).

            Which only works if the collections are really, really small. :)

            1. 3

              Predicate pushdown is a more common name for the concept, which makes its meaning more obvious. You push predicates down the levels of abstraction closer to the data. Applying predicates reduces result set size, so the sooner you apply them, the less data you have to transfer around to other systems.

              But you can also push down other operations. In addition to what @jdegoes said, this shows up a lot in big data type stuff. For example, MapReduce can be done in strictly Map / Shuffle / Reduce phases, but it’s (almost always) better to run the reduce locally on each map node before shuffling the map results over the network.

      2. 7

        LinkedIn login page.

        1. 1

          I didn’t get one, although I no longer have a linkedin account and have never used it on this machine.

          1. 5

            I get one even in a private browsing window on mobile.

            Edit: To add to the mystery, any connection from my home, private window or otherwise, give me a login screen. Using Tor correctly shows me the article. Thanks, LinkedIn.

            1. 2

              LinkedIn is riddled with these sort of slimy practices - I finally got sick of it and deleted my account almost a year ago. Good riddance.

        2. 16

          I have a hard time summoning up sympathy for anybody who bought into the Mongo hype.

          1. 21

            I worked at SlamData. I’ve never thought MongoDB was a reasonable idea. I do think making analytics easy on existing MongoDB stores is a good thing to be achieving.

            How I personally viewed my work was:

            “Hey, I see you’re using a not-great DB and it’s not easy for you to fix that, let me help you in some way”

            I don’t have any problems with that.

            1. 12

              This isn’t a constructive comment, but comes off as really negative.

              A lot of people are using MongoDB. John’s company is trying to make life easier for those people. While doing that, he and his company are dreaming big and trying to enjoy capturing that dream. I can think of only praise and inspiration from him.

              His post isn’t isn’t only about Mongo, but also about the experiences of a software partner, and it’s really interesting and a well-written post.

              1. 15

                It was intended to come across as negative. I don’t know the author, and he might be a great guy. But you make your choices; and it’s not like Mongo as a company hasn’t been a bad actor from the beginning (and their terrible software has never been fit for purpose). If you build your business based on wishcasting the world to be more in tune with your prejudices than it is, you should stand up and take your lumps when it turns out that reality is something rather different than “wouldn’t it be great if shitty software companies didn’t lie all the time”.

                1. 6

                  As puffinfresh points out: it’s not that he bought into the MongoDB hype…it’s that his business was predicated on other people buying into the MongoDB hype and needing to backfill reality to match their expectations.

                  I’ll gladly Waldorf with you about MongoDB and its proponents, but that isn’t quite the case here.

            2. 3

              Oh wow, this is real? I totally thought this was a joke/parody post about an alternate universe.

              1. 1

                Almost everything about this post is annoying ‘:| He also seems to think very highly of himself; a superhero sent to stop MongoDB from making a fatal mistake! But alas! Even he isn’t powerful enough!

                1. -1

                  This guy is just having an extended baaawwww at MongoDB trying to act like a business.