Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Do you still use MongoDB?

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 243 posts

Re: Ask HN: Do you still use MongoDB?

#121

Post by arnejenssen »

Yes. I've been using mongo for various projects for 8+ years. I like the flexibility of the document model. No migration headaches. The query language is powerful and intuitive. I haven't used the graph features yet, but it is nice to know that Mongo can support it if that need ever comes up. I use mongo Atlas as a managed database for peace of mind. I use Redis in addition for caching.

For testing/TDD i use mongo-memory-database. It creates a isolated in-memory instance for each of my test suite, so there is no need for mocking.

Re: Ask HN: Do you still use MongoDB?

#122

Post by doublesCs »

scarface74 wrote: post #109
doublesCs wrote: post #91

Earlier quoted context omitted.

How much memory a device has now does not depend on company culture. How reliable we can expect a future feature to be, does. I think you're making an active effort to misunderstand me.

I’m saying it’s completely illogical to base technical decisions on information that is 10 years old when just like you can see the modern specs of the iPhone and compare to the first iPod, you can also see the modern specs of Mongo, read third party assessments, and even look at the source code to see if it meets your needs.

You have a view of software development so narrow minded to a point it's cartoonish.

Re: Ask HN: Do you still use MongoDB?

#123

Post by whalesalad »

LittlePeter wrote: post #100
dreur wrote: post #62

There is a very recent Jepsen report on MongoDB. http://jepsen.io/analyses/mongodb-4.2.6 > Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and…

I don't understand half of what this means. Does it rule out MongoDB if you care about your data?

Yes.

Re: Ask HN: Do you still use MongoDB?

#124

Post by codr7 »

kgraves wrote: post #107
codr7 wrote: post #103

I've promised myself to never touch MongoDB again. Worked for a valley startup back in 2013 that picked Mongo as primary data store because the CEO liked the simplicity and was too busy with the future to learn anything more complicated. I only implemented a couple of features before I got out of that mess. But from my experience, compared to dozens of SQL and NoSQL databases I've worked with; it was definitely the w…

That was like what, 7 years ago? Do you think this has changed now about Mongo since then?

The best predictor of future behavior is history.

Much like the startup CEO I mentioned, Mongos developers don't really seem to care much about here and now.

Re: Ask HN: Do you still use MongoDB?

#125

Post by ken »

smoe wrote: post #82
josephg wrote: post #27

No. Every time I've used mongodb we've ended up regretting it for one reason or another. And migrating to a different database after launch is a huge hassle. I've done a couple projects where we kicked off with postgres using JSONB columns for early iteration. Then we gradually migrated to normal SQL columns as the product matured and our design decisions crystallized. That gave us basically all the benefits of mongo…

I never understood the appeal of the JSON to SQL columns workflow. At least with the ORM(-ish) tools I worked with, it always felt much more straightforward to just change classes within the application code and automatically generate the respective migrations files to be run on the relational database, than having to interact as a human with json (for the app as well as for business intelligence and reporting/monito…

> At least with the ORM(-ish) tools I worked with, it always felt much more straightforward to just change classes within the application code and automatically generate the respective migrations...

There's your answer, no? You've got specific tools and workflows you've designed to work with your database in a specific way. You can't just take one workflow and substitute a piece of another workflow and expect it to always work. Your tools and processes would be as useless for me as mine would be for you.

Re: Ask HN: Do you still use MongoDB?

#126

Post by jFriedensreich »

LittlePeter wrote: post #100
dreur wrote: post #62

There is a very recent Jepsen report on MongoDB. http://jepsen.io/analyses/mongodb-4.2.6 > Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and…

I don't understand half of what this means. Does it rule out MongoDB if you care about your data?

yes, caring about your data and mongodb used to be even more opposites than now, but even with the improvements it's not a good fit.

Re: Ask HN: Do you still use MongoDB?

#127

Post by john-tells-all »

gnulinux wrote: post #77
tmlee wrote: post #68

Earlier quoted context omitted.

While there are many people here who are sharing their bad experience with MongoDB, just curious if you all find the experience with DynamoDB similar? Since they are both of the NoSQL family.

I'm curious as well, since my company is moving from Postgres to DynamoDB.

Could you share your use case?

Re: Ask HN: Do you still use MongoDB?

#128

Post by mbell »

damidekronik wrote: post #92
mbell wrote: post #88

Earlier quoted context omitted.

> We're not going to be migrating terabytes of data You may have dramatically less 'real data' than mongo makes you think you do. I migrated one of our mid sized database out of mongo and into PG a couple years ago. The reduction in size was massive. One table in particular that was storing a small number of numeric fields per doc went from ~10GB to ~50MB. I wouldn't expect this with all datasets of course, but mongo…

Not OP but I think it's more about the importance of the said data, number of collections to think about and so on. Regarding your point, I would guess some index changes might have had a significant impact here.

> Regarding your point, I would guess some index changes might have had a significant impact here.

I'm not sure exactly what you mean, but that particular collection only had a single index on it (outside the ID column).

Post reply on HN