But saying this would not make for a blog post. I can’t help but categorize this post as juvenile at best. Generalizations like “use XXX for everything’ should be avoided at all costs. No software product serves well to such sweeping generalizations. I’m surprised that it’s coming from a CTO. They should know better if they’re worth their salt .
"Just use the right tool for the job at hand."
Yes, but I have heard exact that phrase for decades to rationalize tech decisions for tools that weren't needed.
I know you're different, but think of all the people who have the same problems.
If you need complexity b/c you're Netflix or Uber, go ahead. If you're the 95% others who don't need that complexity, then don't do it.
"I can’t help but categorize this post as juvenile at best."
Thanks, I guess this is the nicest thing to say to someone 50+!
Your username is also juvenile, well done you!
Fwiw, my experience has also led me to be on the side of "just use Postgres" unless required otherwise. I've seen enough people glue whatever crazy technologies together where a relational database would've been enough.
It was Codemonkeyism before (𝅘𝅥𝅮 "Code Monkey think maybe manager want to write god d** login page himself") but I thought I had grown to be king of the asylum.
No matter the scale or how big it is.
If you are talking of specialized solutions, that means you know exactly where an existing, well known solution is failing you and why.
Eg. if you drop all foreign key references and constraints in Postgres, you might get similar write performance to other databases which can't make those guarantees when you do need them.
Postgres is an all-purpose database that has it all: relational databases were created to model real world problems, and while they might not perform best for all the usecases, they can usually model them just fine while protecting from many programming errors.
And then Postgres has features on top: partial indexes, object DB features, replication etc.
That's Postgres.