4 ms·
I thought all those points died along with the hype ("MongoDB is web scale"), as all were wrong. Those were the marketing points people mentioned in their "hon
by coldtea 3y ago
I thought all those points died along with the hype ("MongoDB is web scale"), as all were wrong.
Those were the marketing points people mentioned in their "honeymoon phase" posts. Then after using it in production, actual benchmarks and comparisons coming in, came the regret and moving on posts. In fact, most of those mentioned moving from Mongo to Postgres, and there was a full blow "yeah, NoSQL was a dumb idea for 99% of use cases, and Mongo even more so" discussion.
In the end MongoDB was the butt of a joke, there were whole memes about it.
So this comment is like a trip down memory lane, or into an alternate universe, where it's like 2012 and these things never happened.
- isoprophlex 3y agoYou're wrong. MongoDB is web scale. /s
- re-thc 3y agoBut is it PlanetScale?
- romanovcode 3y agoIt's not 2012 anymore ;)
- seedless-sensat 3y agoHow is (a) wrong? Pg doesn't horizontally scale like Mongo does
- re-thc 3y ago> Pg doesn't horizontally scale like Mongo does At what cost though? Does 1 Pg server = 1 Mongo server for the same specs or do you need a lot more Mongo servers?
- coldtea 3y agoBetween plain old horizontal scaling via custom sharding, replicas, and extensions like Citus and Timescale that offer full horizontal scalability, Postgres is handling some of the biggest use cases in the world.
- endisneigh 3y agoIt's simply a fact that Postgres does not offer out of the box scaling like MongoDB. Postgres does have things like Citus, or even wire-protocol compatible things like CockroachDB that do scale, but those are not Postgres. It's the same situation with MySQL vs. Vitess.
- riku_iki 3y ago> but those are not Postgres. sure, citus is an extension of postgres and part of ecosystem.
- hot_gril 3y agoAnd it comes with a bunch of caveats. It's bolted-on horizontal scaling, vs MongoDB where that's the main feature. Yes I still prefer Postgres in general, but it's fair to point out that weakness of it.
- threeseed 3y agoCitus was acquired by Microsoft so there are doubts about its future longevity given that so many similar promises of ongoing support are rarely maintained. Timescale is optimised for time-series so not sure it's applicable. Point still remains that PostgreSQL lacks a modern, built-in horizontal scalability solution.
- coldtea 3y ago>given that so many similar promises of ongoing support are rarely maintained Microsoft on the other hand is among the best in keeping such promises. If Google had bought it, sure...
- hot_gril 3y agoWell let's see how long Google's Spanner lasts. It's designed to support huge-scale systems, and personally I'd be terrified locking a huge system into that.
- romanovcode 3y agoOkey, maybe I do not understand something but how is https://neon.tech https://neon.tech not auto-scaling? Or the more expensive option at AWS Aurora?
- endisneigh 3y agoThis is not Postgres. It's a managed instance, but isn't built in.
- re-thc 3y ago> not auto-scaling? The writes aren't. There's no sharding for example. You can ever only have 1 primary writer.
- maxbond 3y agoFair, but this is getting fixed. Postgres 16 (which was just released) adds an origin tag to logical replication, so that you can know whether or not to pass on a change (and avoid having an infinite loop where a change is replicated back and forth). That's the first step to having multiple mains. I think in theory, if you had deep Postgres knowledge, you could set up a high touch, bespoke multi-main deployment today. I expect the replication story with Postgres will get much better over the next few years.
- threeseed 3y agoAt least in my experience it is all still the case today. If you are dealing exclusively with documents I find MongoDB to be faster, better and easier to use. If my data model is hybrid or purely relational then I would use PostgreSQL. After all these years I am still waiting for an horizontal scalability solution for PostgreSQL that is up to the level of a modern database. It's 2023 and for many of us in enterprise environments it's a mandatory NFR. But it seems like you're not interested in a having an actual technical discussion.
- coldtea 3y ago>But it seems like you're not interested in a having an actual technical discussion. You mean like the "technical" bullet points that could just as well be marketing copy?
- prmoustache 3y agodid you try citus? https://www.citusdata.com/product/community https://www.citusdata.com/product/community
- deleted 3y ago[deleted]
- aeyes 3y agoIt has serious limitations and needs a lot of elbow grease to run at scale. With some of the alternatives (for example MongoDB) you basically just add a few more machines and you are good. In my opinion Citus is still only a hack which is only useful if for some reason you can't move away from Postgres but you have reached the limit of what you can get out of a single machine.
- nesarkvechnep 3y agoWell, your data model could become relational if you normalize it.
- skywhopper 3y ago
- LtWorf 3y agoThey used it at my first full time job out of university. It was terrible. It was not fast, a regular SQL db would have been much better, due to bugs in our code, the data in mongodb was not uniform, which led to failures in the code when the document didn't have the expected format. Cherry on top is that they were mostly growing documents, which is a very slow operation, that would have been done very fast with a many-to-many table in SQL instead.
- fkyoureadthedoc 3y ago> due to bugs in our code, the data in mongodb was not uniform It supports schemas though right? https://www.mongodb.com/docs/manual/core/schema-validation/ https://www.mongodb.com/docs/manual/core/schema-validation/
- deleted 3y ago[deleted]
- VancouverMan 3y agoIf I'm not mistaken, that was added relatively late, in version 3.2, which was released in December 2015.
- skywhopper 3y agoIt all depends on your data structure and problem space. It was silly to dismiss RDBMSes as obsolete 10 years ago, and it's silly to dismiss document databases or other NoSQL databases today. There are plenty of use cases for which Mongo is far superior to Postgres. A wise engineer chooses the best tool for the job.
- jameshart 3y agoIf you base your technology decisions on what the current memes are on /r/technology, you're going to have that impression, sure. But in reality, no, there wasn't a vote held in 2016 where we all agreed NoSQL was a mistake and we should go back to RDBMSs. The horizontal replication story in Mongo is just a different game. And because it's so reliable, that ends up being how you solve not just availability and scalability but also engine upgrades and config changes. I migrated a bunch of production transactional databases on Mongo Atlas from a GCP cluster to an AWS cluster, with zero read/write downtime, by just walking through simple cluster reconfiguration steps. Add some nodes in AWS... move the write master... remove some nodes from GCP. It was stress free and easy. The same trick with replication on Postgres was a nail biter every time we did it.