4 ms·
The biggest problem seem to be microservices. Basically, an army of cargo culters missed the small print that you should not even be thinking about them unless
by cjfd 5y ago
The biggest problem seem to be microservices. Basically, an army of cargo culters missed the small print that you should not even be thinking about them unless you work with at least 100 programmers. The talking heads that popularized microservices are also guilty of this. They occasionally mention that microservices are only for large teams but not nearly often enough.
- comeonseriously 5y agoCargo culting is just what you have to learn to accept and work around, because there will always be developers who fall for it. A decade ago, everyone was writing dependency injection frameworks because that was the hotness and debugging became a nightmare, but, hey!, we completely decouple EVERYTHING! Then there was no sql (mongo etc) and if you were still using sql, your system was shit. Oh and way before that there was GoF and you ended up with UserBillingFacadeFactoryFactory abstractions. None of these technologies are bad. They're just bad in the hands of mediocre developers.
- packetlost 5y agoYes and no. There are legitimate reasons to build microservices with small teams (such as requiring differing runtime environments due to hardware/architectural constraints). They should never be the default at a team below that scale though.