kenwalger's comments

Some very nice and thoughtful work done here. One of the security risks that I see is the passing of corporate information into ChatGPT which may be sensitive. Is there a way to obfuscate that potential issue in an automated fashion?

There are many, many companies that rely on MongoDB. Companies like Google, Facebook, Cisco, Expedia, eBay, just to name a few.

In my experience data loss and operational issues are a thing of the past. With the current version of MongoDB, 3.6, there are lots of data safeguards in place. One of the biggest frustrations that any company faces in the age of the internet is old topics of discussion. MongoDB has come a long way since many "problem area" blog posts and articles.

If you haven't tried out the latest version and put it through its paces, I would highly encourage you to do so. Judging by reports of others here as well as performance and security analysis done by outside vendors, MongoDB is truly web scale.

I've written my own blog posts on MongoDB Performance (https://www.kenwalger.com/blog/nosql/mongodb/mongodb-perform...) and Data Durability (https://www.kenwalger.com/blog/nosql/mongodb/data-durability...) which, while based on MongoDB 3.4, still offer some useful insights into the current state of MongoDB.

Try it out and report back your own findings.

MongoDB is definitely ready and capable of handling your traffic. There are best practices to follow, however, as is the case with any deployment. I would concur with mattbillenstein that HN definitely skews anti-mongo.

There are many, many companies using MongoDB very successfully. I have found that "issues" being reported with MongoDB are based on old versions and information, or an improperly configured and tuned environment. I recently wrote a blog post covering some topics around this. I'd encourage you to read it: https://www.kenwalger.com/blog/nosql/mongodb/mongodb-perform...

I think you'll find that MongoDB will meet, and exceed, your expectations for performance.

These "Why technology X is worthless" types of posts and statements always give me a bit of a laugh. As with most technologies, there is a) a learning curve, and b) best practices to follow.

Many of the comments here seem to discuss a few things which, in my opinion, lead me to believe that the implementation is incorrect or decisions are being made on old data or based on older versions of MongoDB. Making arguments against any product based on previous versions seems to be counter productive. Most of the posts here don't make reference to a specific MongoDB version, but many reference their experience with the product in 2012.

Assuming that these experiences were at the end of 2012 with the most current at the time version, we are still talking about version 2.2.2. The current stable version is 3.4.6. As you can imagine, there have been many advances to the product in five years. Basing one's knowledge and opinion of MongoDB on old versions doesn't seem logical. Even back in 2012 though, there was a lot of misinformation about MongoDB. A blog post from that time period (https://blog.serverdensity.com/does-everyone-hate-mongodb/) argues some of that information at that time.

Many other comments were made based on what seems to be a lack of spending time with learning MongoDB. It is a non-relational document store. It is NOT a relational database. It requires a different way of storage design and thinking and attempting to force MongoDB to be a SQL-like database is silly. SQL is indeed a popular option and can work well.

However, non-relational databases work well too. There are lots of implementations of it across a lot of companies. A few relatively recent posts are good examples https://engineering.snagajob.com/mongodb-in-aws-does-it-real... and https://mongomikeblog.wordpress.com/2016/04/29/why-we-went-w... That doesn't account for many of the large companies out there using it, like Expedia, Facebook, Forbes, to name a few.

If we want to have a discussion about specific, current, features of MongoDB, that's great. There are a lot of them. Many have been mentioned. Some have been mentioned as a negative due to what appears to be poor implementation. If we want to debate pros and cons of any product, we should be sure that we are talking about how things are intended to be implemented and not some hacked together approach.

Perhaps the marketing spin was too aggressive. I'm not a marketing person. I'll leave it to Mr. Horowitz to backup his claims. But if we are going to have a discussion about the pros and cons of MongoDB, can we at least agree to not talk about old versions? I mean, I had a bad experience with Windows 3.1, so should I not use Windows anymore? ;-)

MongoDB Stitch is a great new BaaS offering. They even have some great tutorials online to use it.

Have a look at their sample PlateSpace app: https://github.com/mongodb/platespace

Very cool new service and some excellent tutorials as well, for example for the PlateSpace web app: https://docs.mongodb.com/stitch/getting-started/platespace-w...

I'd definitely recommend having a look.

These are all incredible new features! Way to go MongoDB.

I'm really excited about the new UI features and queryable backups.

MongoDB 3.4 passes the rigorous and tough Jepsen test. Jepsen designs tests to make databases fail in terms of data consistency, correctness, and safety... MongoDB 3.4 passed through their newest tests.

I think that this really shows how mature of a Database MongoDB is.