Goodbye MongoDB, Hello PostgreSQL (2015)
developer.olery.com
Goodbye MongoDB, Hello PostgreSQL (2015)
1–10 of 172 posts
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#2I learned a framework several years ago and its default db was MongoDB. So I worked with MongoDB for a few years. Then at my job I used PostgreSQL for a several months. I will probably never use MongoDB again.
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#3Previous discussion from 2015: https://news.ycombinator.com/item?id=9178773
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#4MongoDB is like snapchat for database
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#5I used both NoSQL and SQL databases. Proper replication topologies (e.g. multi-master configurations) and JSON columns killed the NoSQL movement. I'm glad the NoSQL movement existed and forced the SQL camp into out-of-the-box thinking, but I wouldn't go for any NoSQL solution today on a greenfield project.
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#6This is from 2015. I wonder if it is the same in 2021. Anyone running high throughput/low latency services using MongoDB?
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#7MongoDB and Postgres have very different strengths and weaknesses. It sounds like they didn't consider the needs of their read and write patterns before they decided to go with MongoDB and then blamed it for not being a good fit for their use case. The article doesn't give any insight at all into the cause of the performance issues, just that they happened. It could've been that they were doing something inefficiently. They also don't give any reasons for the performance increase when switching to Postgres. It could've been anything like they were doing application layer joins with Mongo and things got faster when switching to a relational database because they could do joins in one process without serially fetching data over the network. They also touch on schema on read vs schema on write but instead of talking about the tradeoffs and use cases of both patterns, they just claim schema on read is bad.
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#8Previous discussion from 2015: https://news.ycombinator.com/item?id=9178773
The top comments of this old thread are retrospectively hilarious because sone frontend guys argues about wether SQL is not easily composable and exchanges trick about how you can securely and dynamically concatenate SQL statements.
But nowhere to be found is the concept of prepared statements that would gracefully help then write nicer code. https://www.postgresql.org/docs/current/sql-prepare.html
And that is a lightweight in-code solution for those who are repelled by database procedures which is yet another way to solve theirs issue with SQL.
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#9What surprises me is that so far none shoehorned Postgres on top of FoundationDB.
Re: Goodbye MongoDB, Hello PostgreSQL (2015)
#10I'm a designer and front-end developer. I'm building a fullstack project by myself in Node and I'm using MongoDB.
Can someone tell me why is it so bad?
I've searched for concrete answers but I got none for the moment yet from time to time people say these kind of things and I worry.