Live data from Hacker News

Ask HN: Do you still use MongoDB?

news.ycombinator.com

31–40 of 243 posts

Re: Ask HN: Do you still use MongoDB?

#32
MongoDB was only really ever a competitor to memcached, redis, others and really only good as a caching layer like those. It is decent for that.

There was a time when JSON wasn't that integrated into databases, it is now. That was really MongoDB's killer feature.

PostgreSQL does most of this better now and more robust/reliable.

Re: Ask HN: Do you still use MongoDB?

#33
post #18

Yes, still using it for storing relatively unstructured blobs of JSON which I only lookup via key but update with various operators ($addToSet, $set, $incr). Also using it as a persistent session store and lately for storing rate-limiting information. I've come to like the MongoDB update operators and features such as the Change Events. However I will eventually be moving off MongoDB as I need horizontal scaling via…

Atlas makes sharding easier, it's just one button where you define your partition key.

Re: Ask HN: Do you still use MongoDB?

#34
Yes, we do at WaystoCap. It's our main DB. I like it mostly for the flexibility. I think it's one of the best DBs when you're in pre-product market fit stage and making a lot of changes to the data model.

One of the main cons I've experienced with it, is it's beginner friendly nature and docs leads you to have a non-optimal data schema for No-SQL. Like even the way it does pagination with Skip, is not the performant way to do it.

As areas in our business mature and scale we suffer bottlenecks and have pretty big changes to optimize those areas of the data model.

Re: Ask HN: Do you still use MongoDB?

#35
I have not used it for years. I simply prefer relational databases after all.

When a document database makes sense, it happens, I go with CouchDB. Its multi-primary architecture is attractive compared to MongoDB with a single primary node. But I'm thinking about using PostgreSQL and jsonb next time.

Re: Ask HN: Do you still use MongoDB?

#36
post #14

Earlier quoted context omitted.

jsonb is limited in it's querying capabilities. you're essentially casting the json as a string when storing and querying, it's not truly json. therein lies the advantage of document model, native secondary indexes, $ for everry nested layer, etc.

Postgres's jsonb format is definitely not "essentially" a string. You can get native indexes on json fields in Postgres, and you can query fields however you like.

https://www.postgresql.org/docs/9.5/functions-json.html

they are surrounded by quotes, is that not a string ?

Re: Ask HN: Do you still use MongoDB?

#37
post #22

Yes, use it with Atlas for every one of my companies' projects. - The document model is a no-brainer when working with JS on the front-end. I have JSON from the client, and Dictionaries on the backend (Flask), so it's as easy as dumping into the DB via the pymongo driver. No object relational mapping. - Can scale up/down physical hardware as needed so we only pay for what we use - Sharding is painfully easily, with o…

This is a great testimonial. Would you care to share what Atlas is/which software package Atlas is?

Re: Ask HN: Do you still use MongoDB?

#38
post #6

No, I had a sour experience in 2009 where it ate my data, the devs were rather cavalier with "there's a warning on the download page" (I got it through apt), it ate my data again when the OOM killer killed its process. I didn't like the project attitude of a database being so lax with persistence, so I never used it again.

I'm the most popular non-MongoDB-employee answer at 'to what extent are 'lost data' criticisms still valid of MongoDB?'

My answer contains a history of my experiences with MongoDB that is pretty similar to yours:

https://stackoverflow.com/a/18269939/123671

I feel like MongoDB now is actually a pretty stable product simply through time and investment, however I will never trust the company for using our data to beta test for a decade.

Re: Ask HN: Do you still use MongoDB?

#39
post #33
post #18

Yes, still using it for storing relatively unstructured blobs of JSON which I only lookup via key but update with various operators ($addToSet, $set, $incr). Also using it as a persistent session store and lately for storing rate-limiting information. I've come to like the MongoDB update operators and features such as the Change Events. However I will eventually be moving off MongoDB as I need horizontal scaling via…

Atlas makes sharding easier, it's just one button where you define your partition key.

No offense, but if I wanted to have managed MongoDB I might as well use AWS DocumentDB.

I honestly believe that this is a key differentiating feature for many databases. ElasticSearch, ScyllaDB, others too work the same way: Every node is equal and in order to scale you just keep adding more boxes, end of story. Compare that with what you have to do with MongoDB.

Post reply on HN