5 ms·
Radical Simplicity in Technology
- dzonga 2y agothis works if you work in typical crud apps - where 1. you never need to talk to external api's 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
- wild_egg 2y agoNot sure where you're getting those requirements from — message queues were called out specifically in TFA and async workflows are trivial to build on top without instantly reaching for Kafka 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
- people_skills 2y agoMy colleagues: spend hours figuring out how to make radically simple interface like google.com page work for thousands of users simultaneously Author: just remove unnecessary architecture :-)
- Borg3 2y agoOh comeone people. Answer is simple. Money! Complexity means more money, means spending for developers are justified! Its so complicated after all! Simple solutions that just works will not pay you bills.