Ask HN: Do you still use MongoDB? • Hacker News Board

Re: Ask HN: Do you still use MongoDB?

#241

Post by 40four » Wed, May 27, 2020, 3:35 PM UTC

dynamite-ready wrote: post #240

40four wrote: post #237

Earlier quoted context omitted.

Thanks for the CouchDB feedback guys! I am curious to try it out. I should have been more clear, I was actually referring to Couch base ( https://www.couchbase.com/ ) not CouchDB :) Very unfortunate naming conflict considering they are both JSON document stores. Is there something about the word 'couch' that I'm missing? From my experience with Couchbase though, I would recommend it to others. They support SDKs in ma…

Couchbase was a commercial CouchDB spinoff product, co-created by the programmer who created CouchDB. Much of the API is (was?) the same, but where possible, Erlang was exchanged for C++. It also has a built-in, in-memory cache layer, which CouchDB doesn't have.

Oh wow, thanks. I didn’t know the history of it!

Re: Ask HN: Do you still use MongoDB?

#242

Post by jaydestro » Fri, May 29, 2020, 1:18 PM UTC

hartror wrote: post #215

danenania wrote: post #189

Earlier quoted context omitted.

DynamoDB is a lot more explicit about its tradeoffs. Much of the backlash against Mongo was because it basically claimed to be well-suited to any use case, when its sweet spot was really far narrower. To be successful with Mongo, you need to design the entire app around its limitations, but those limitations were initially downplayed and obscured. People were convinced that Mongo was a good choice as a default, gener…

What are those good use-cases for mongo?

I worked for a big news website- we used mongodb for pixel tracking data.

I went on to work at mongodb

Re: Ask HN: Do you still use MongoDB?

#243

Post by hodgesrm » Sat, May 30, 2020, 5:23 PM UTC

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…

The JSON-to-columns approach is a best practice for analytic applications. ClickHouse has a feature called materialized columns that allows you to do this cheaply. You can add new columns that are computed from JSON on existing rows and materialized for new rows.