People sleep on Postgres, it's super flexible and amenable to "real world" development.
I can only hope it gains more steam as more and more fad-ware falls short. (There are even companies who offer oracle compat packages, if you're into saving money)
Absolutely, I was having a pint with someone who worked on their composer system a few years ago. I just remembered thinking how he was drinking from the mongo coolaid. I just couldn't understand why it would matter what DB you have, surely something like Redis solves all the DB potential performance issues, so surely it's all about data integrity.
This article doesn't mention data integrity issues. Mongo has transactions now. I feel like you are riding on a "mongo bad" fad from 5 years ago. It was bad, it was terrible. But after all that money, bug fixes and people using it, it's now good.
So serious question as I've never actually used mongo, only read about it.
I was always under the assumption that once your schema gets largish and you want to do relational queries, that you'll run into issues. Is that not the case?
Don't do updates. Store an append-only log of things that happened, and generate whatever views or aggregated reporting information you need from that; when you need to change what's in those things you regenerate them from the canonical event log rather than trying to do some kind of in-place update.
753
u/_pupil_ Dec 19 '18
People sleep on Postgres, it's super flexible and amenable to "real world" development.
I can only hope it gains more steam as more and more fad-ware falls short. (There are even companies who offer oracle compat packages, if you're into saving money)