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

Ask HN: Should I not use MongoDB?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 28 posts

Re: Ask HN: Should I not use MongoDB?

#11

Post by jd_mongodb »

smt88 wrote: post #4

The hatred and fear of Mongo is justified. That doesn't necessarily mean you need to switch right now. If you're just using a document DB instead of a relational DB, you won't have a hard time moving away from Mongo. There just isn't that much to learn. Even better, there are various databases that actually have Mongo compatibility[1][2], but internally will be more reliable and scalable. If you have the dev bandwidt…

'Hatred and fear" ? This is a database we are talking about?

Companies all over the globe are betting their businesses on MongoDB and succeeding.

e.g. most recently Ticketek

http://www.theaustralian.com.au/business/technology/mongo-mi...

Re: Ask HN: Should I not use MongoDB?

#12

Post by jaydestro »

jd_mongodb wrote: post #11
smt88 wrote: post #4

The hatred and fear of Mongo is justified. That doesn't necessarily mean you need to switch right now. If you're just using a document DB instead of a relational DB, you won't have a hard time moving away from Mongo. There just isn't that much to learn. Even better, there are various databases that actually have Mongo compatibility[1][2], but internally will be more reliable and scalable. If you have the dev bandwidt…

'Hatred and fear" ? This is a database we are talking about? Companies all over the globe are betting their businesses on MongoDB and succeeding. e.g. most recently Ticketek http://www.theaustralian.com.au/business/technology/mongo-mi...

mongodb employee here

https://www.mongodb.com/who-uses-mongodb

I don't see a ton of hatred and fear from Cisco, Facebook and Google.

I dig what they've done, especially facebook, with MongoDB. Reconsider 2012 opinions and read about 2017's MongoDB.

Re: Ask HN: Should I not use MongoDB?

#13

Post by giaour »

Running your own Mongo instance will probably be fine for now. I remember Mongo administration being a massive time sink, but it only gets truly hairy when you need to shard and cluster. You can always use a hosted Mongo instance or a hosted Mongo-compatible solution like CosmosDB.

Re: Ask HN: Should I not use MongoDB?

#14

Post by mikegray831 »

Another user of MongoDB here. Thus far it has scaled well for us where we had a similar situation where uptake was faster then expected. The WiredTiger storage engine made most of the concerns of 2012-2013 for MongoDB, non-issues. However, if you try to put a relational model in to MongoDB, you still may see performance issues down the road, but then again it should be about the right tool for the right job. I'd reiterate Ken Walger's post to checkout his blog, it does a great job of comparing MongoDB 2012 vs. MongoDB today. Also, if administration/operations are a concern, then cloud provided MongoDB is the way to go, MongoDB Atlas seems to be at the forefront since it's run by MongoDB itself. Good luck with your apps!

Re: Ask HN: Should I not use MongoDB?

#15

Post by smt88 »

jd_mongodb wrote: post #11
smt88 wrote: post #4

The hatred and fear of Mongo is justified. That doesn't necessarily mean you need to switch right now. If you're just using a document DB instead of a relational DB, you won't have a hard time moving away from Mongo. There just isn't that much to learn. Even better, there are various databases that actually have Mongo compatibility[1][2], but internally will be more reliable and scalable. If you have the dev bandwidt…

'Hatred and fear" ? This is a database we are talking about? Companies all over the globe are betting their businesses on MongoDB and succeeding. e.g. most recently Ticketek http://www.theaustralian.com.au/business/technology/mongo-mi...

I hate and fear lots of technologies. When you struggle against a bad technology decision at a company for weeks, months, or years, hatred/fear is justifiable.

Luckily, I don't care what "companies all over the globe" are doing. I'm paid to know the difference between cargo-cult decisions and good decisions.

Interesting to see Mongo's (in)famous marketing in action again, though![1] I'll stick to equally-or-more popular products that succeeded on technical merits instead of marketing (e.g. Postgres).

1. https://www.nemil.com/mongo/3.html

Re: Ask HN: Should I not use MongoDB?

#16

Post by smt88 »

jaydestro wrote: post #12
jd_mongodb wrote: post #11

Earlier quoted context omitted.

'Hatred and fear" ? This is a database we are talking about? Companies all over the globe are betting their businesses on MongoDB and succeeding. e.g. most recently Ticketek http://www.theaustralian.com.au/business/technology/mongo-mi...

mongodb employee here https://www.mongodb.com/who-uses-mongodb I don't see a ton of hatred and fear from Cisco, Facebook and Google. I dig what they've done, especially facebook, with MongoDB. Reconsider 2012 opinions and read about 2017's MongoDB.

Instead of insulting me with the implication that I don't keep up with major technologies in my industry, you probably would've been more convincing if you'd told me what's changed since 2012. However, I do keep up with Mongo, and I do know what's changed.

It still doesn't make me want to use it. Relational data is better for most applications, Redis is better for many others, and I can have both documents and relational data in the same database with PG[1].

It seems like many other people with Mongo experience feel the same way[2].

1. http://www.aptuz.com/blog/is-postgres-nosql-database-better-...

2. https://news.ycombinator.com/item?id=15125984

Re: Ask HN: Should I not use MongoDB?

#17

Post by brianwawok »

gerenuk wrote: post #7
mattbillenstein wrote: post #2

HN skews very anti-mongo, but it can be a good fit for certain apps -- I would stick with what you know until you think you've outgrown what you can do without sharding. I'd probably never shard mongo, but if you can vertically scale it for awhile, I'd do that. If you're on ec2, the i3 instances have very fast nvme instance storage at a reasonable (cloud) price.

What would you suggest instead of mongodb for large scale production db? Our DB size is growing on daily basis and currently near to 200GB on a dedicated machine.

Postgres or cassandra depending on scale and use case.

Re: Ask HN: Should I not use MongoDB?

#18

Post by brianwawok »

jaydestro wrote: post #9

hey there, i am a person from mdb: one thing i should express, many of the negative sentiments of mongodb are related to outdated facts or commentary. review some of the new features to ensure you're getting all the benefits mongodb has produced since the days of 2012.

So? Its still not a great product. People use it because they don't know better. Those that know better dont use mongo.

Re: Ask HN: Should I not use MongoDB?

#19

Post by dsirola »

jaydestro wrote: post #9

hey there, i am a person from mdb: one thing i should express, many of the negative sentiments of mongodb are related to outdated facts or commentary. review some of the new features to ensure you're getting all the benefits mongodb has produced since the days of 2012.

That's not the problem in my opinion. The problem is advertising any kind of document DB as a general purpose storage. If you have a use case of making different aggregates from data, you'll have a bad time duplicating data or creating your own consistency layer.

Re: Ask HN: Should I not use MongoDB?

#20

Post by nikkwong »

scalesolved wrote: post #8

"Now that we're figuring out the technology stack for this, I don't want to do work that is going to have to be redone later." You're worrying about problems that you don't yet have and at scales you may never reach. I'd say stick with what you know and see if you can get initial traction with your users. If your data is highly relational then yes it's not a great fit but it's still passable if you're happy to give u…

Yeah, I feel like through using Mongo I've learned how to model my data in ways that are not relational, which has worked well because using aggregation at all always tends to be really awkward.

Agreed that it could go no where, but, I'm hoping that one project, at some point in my life does well—so learning a technology that doesn't suffer from scaling issues would hopefully be a road I eventually have to take.

Appreciate the feedback!

Post reply on HN