Radical Simplicity in Technology
radicalsimpli.city
radicalsimpli.city
Author: just remove unnecessary architecture :-)
2. your work is synchronous
.... out there in the wild, there's plenty of iceberg apps i.e apps that look like crud but are not crud e.g 1. if you're dealing with anything involving money i.e finance whether a portfolio tracker that automatically rebalances your stock you're gonna need a message queue 2. likewise if you call different api's and your workflow is async
The "just use postgres" mantra can take you shockingly far. If you're at a scale where postgres doesn't actually make sense, then you have enough money to figure out and migrate to the best tech for your use case.
Anecdotally, we're processing a few hundred million messages a day through postgres and never have a hiccup. All of our developers already know how to use it so the learning curve and ops burden is essentially zero. We'd have been foolish to pick something else