4 ms·
Completely agree. I remember when Mongo / NoSQL was peak hype cycle, and every new project "needed" to use it despite being a big step down in terms of feature
by collyw 3y ago
Completely agree. I remember when Mongo / NoSQL was peak hype cycle, and every new project "needed" to use it despite being a big step down in terms of features, ability and maturity. A few years later I ended up on a system with Mongo as the database, started when Mongo was at peak hype. It was every bit as bad as I expected.
I have never seen a Mongo Based system that didn't work off of a single server, the one place where it did actually have an advantage.
- tyre 3y agoStripe runs on Mongo, on multiple servers as you can imagine :)
- koromak 3y agoThats wild to me. Payment data is like, the most relational. You need to learn 20 different data models and all their many interconnected relationships just to implement a custom API integration. Maybe thats why it sometimes feels like pulling teeth to get the data you want out of a particular Stripe flow. I used a document db for our side of the billing integration and I really, really wish I hadn't.
- redwood 3y agoI am trying to be constructive here: "Relational" in RDBMS does not refer to what you are implying that it refers to. It's a common misconception honestly. Anyway many interconnected relationships become much simpler to model when you have the richness and flexibility of the document data model.
- TheCondor 3y agoThey have credit card numbers and transaction ids in mongo?
- nkozyra 3y ago> I remember when Mongo / NoSQL was peak hype cycle, and every new project "needed" to use it despite being a big step down in terms of features, ability and maturity. It one for one reason and one reason only - performance over everything else. Any time I'd suggest using MySQL or PG during this period the reactions were as if I'd suggested storing data in a cucumber.
- vkazanov 3y agoI was of the roughly same opinion, especially after getting familiar with relational theory. Despite all the horrors of SQL-the-language, the backing model is close to being universal for data storage and manipulation. Having said that, we did encounter one good use case recently: storing tree-like documents complete with history changes. Mongo-like DBs are really good for this. While possible in relational DBs, this is superinconvenient. Notably, this has nothing to do with performance.
- riku_iki 3y agoservers were having much less RAM, cores and there were no SSD at those time, so NoSql was reasonable for many large scale applications.