Mongodb and postgresql full#
Fancy h'ordeuvres and alcohol flowed freely, and MongoDB's management team was out in full force. Hosted at NASDAQ MarketWatch, in a beautiful space overlooking Times Square, I felt distinctly underdressed in my cargo pants and startup t-shirt. SlamData, my new analytics startup, was sponsoring MongoWorld 2015, so I got a rare ticket to the VIP party the night before the conference. The story begins on June 1st 2015, at the annual MongoWorld conference in New York City. This is the story of what I discovered, how I pieced together the clues from press releases, YouTube videos, and source code scattered on Github, and how I ultimately failed to convince MongoDB to change course. My earlier success in helping convince MongoDB to reverse course when they tried to monetize the wrong feature would not be repeated. I would never hear back from Asya - or anyone else about the matter. While polite, I made my opinion crystal clear: MongoDB is about to make a giant mistake, and should reconsider while there's still time. So when I uncovered a secret this destructive, I hit the panic button: on November 12th, 2015, I sent an email to Asya Kamsky, Lead Product Manager at MongoDB.
In fact, I just presented to a packed room at MongoDB Days Silicon Valley, making a case for companies to adopt the new database. I work on an open source analytics tool that connects to NoSQL databases like MongoDB, so I spend my days rooting for these next-generation database vendors to succeed. If I was right, MongoDB was about to make what I would call the biggest mistake ever made in the history of database companies.
When I finally pieced together all the clues, I was shocked. Opinions expressed are solely my own, and do not express the views or opinions of my employer.
0 kommentar(er)
