2 ms·

How can we know he used Mongo properly or not? Choosing Mongo because you don't know SQL doesn't seem valid. Likewise, choosing Mongo because "JSON is comfortab

How can we know he used Mongo properly or not? Choosing Mongo because you don't know SQL doesn't seem valid. Likewise, choosing Mongo because "JSON is comfortably built into Python" doesn't seem valid. Also, that's harder to do a proper Mongo implementation than to do a SQL implementation. At a former workplace, when I stress tested the same API with different backend databases wired to it, Mongo was faster than Postgres. But we ended up using Postgres + Redis, because that combo was even faster than Mongo.

hot_gril 3y ago
He did say he's not an expert. If anything it's meant as advice for others with small projects. "I'm trying to stay humble. Mongo must be an incredibly big project with lots of nuance. I'm just a solo developer and absolutely not a database engineer. I've also never had the opportunity to work closely with a good database engineer. However I shouldn't be seeing improvements like this with default out of the box PostgreSQL compared to all the things I tried over the years to fix and tune Mongo." But I would not assume that people in bigger companies are always experts in what they deal with either. It kinda matters how well something performs in non-ideal scenarios.
zulban 3y ago
Author here. > How can we know he used Mongo properly or not? You don't. I don't. This is just my story where I'm clearly not a junior but had a ton of problems with mongo. >Choosing Mongo because you don't know SQL doesn't seem valid Valid is such a strange word here. People choose technologies based on their current skills all the time. If you've never encountered that kind of decision before then you need more experience.
Atotalnoob 3y ago
He shouldn't have to "use it properly" He has a smaller website and should be able to use mongo out of the box. Complaining he didn't do indepth optimizations is ridiculous. He picked 2 database products and used out of the box configs. Mongo should adjust their defaults if the defaults aren't using the product correctly

hot_gril 3y ago

He did say he's not an expert. If anything it's meant as advice for others with small projects. "I'm trying to stay humble. Mongo must be an incredibly big project with lots of nuance. I'm just a solo developer and absolutely not a database engineer. I've also never had the opportunity to work closely with a good database engineer. However I shouldn't be seeing improvements like this with default out of the box PostgreSQL compared to all the things I tried over the years to fix and tune Mongo." But I would not assume that people in bigger companies are always experts in what they deal with either. It kinda matters how well something performs in non-ideal scenarios.

zulban 3y ago

Author here. > How can we know he used Mongo properly or not? You don't. I don't. This is just my story where I'm clearly not a junior but had a ton of problems with mongo. >Choosing Mongo because you don't know SQL doesn't seem valid Valid is such a strange word here. People choose technologies based on their current skills all the time. If you've never encountered that kind of decision before then you need more experience.

Atotalnoob 3y ago

He shouldn't have to "use it properly" He has a smaller website and should be able to use mongo out of the box. Complaining he didn't do indepth optimizations is ridiculous. He picked 2 database products and used out of the box configs. Mongo should adjust their defaults if the defaults aren't using the product correctly