2 ms·
Micro-services are currently on trend so hard to argue with unless you are a founder. Maybe the best thing to do for the industry in general is go absolutely nu
by osigurdson 4y ago
Micro-services are currently on trend so hard to argue with unless you are a founder. Maybe the best thing to do for the industry in general is go absolutely nuts with microservices. Factor projects so every method is a separate service / lambda. If anyone complains, use the single responsibility principal to snuff out all opposition.
Once we've explored this to its logical conclusion the pendulum will swing back to something more logical. Of course, it will swing too far and the cool kids will only want to work on monoliths even when it doesn't make sense (kind of like what is happening now with SQL maximalism).
- zo1 4y agoI got tired of arguing against microservices just like I got tired of arguing against SPAs and multi-repos. And at least with one of them, the pendulum has already started swinging back. The cool-kids (aka "javascript hipster devs") have re-discovered the concept of a monorepo and are pushing for it hard, making it seem like some sort of new concept with fancy tooling. It'd be funny if it wasn't so caricatured and a sad state of our industry.
- osigurdson 4y ago>> re-discovered the concept of a monorepo Monorepo and monolith are somewhat orthogonal. The desire to use a monorepo likely stems from wanting to emulate Google.
- take-10 4y ago[flagged]