4 ms·
1) False dichotomy. Developer familiarity is one of the most important metrics for choosing "the best tool for the job". 2) Conway's Law applies in reverse her
by majewsky 10y ago
1) False dichotomy. Developer familiarity is one of the most important metrics for choosing "the best tool for the job".
2) Conway's Law applies in reverse here: If your organization consists of a lot of rather disjoint teams, then microservices can be quite beneficial because each team can deploy independently. If you're one cohesive team, there is not much benefit, only cost.
3) Depends. If you have a well-designed distributed system, it can be amazingly resilient and reliable without introducing much administrative overhead. (From my experience, OpenStack Swift is such a system. Parts may fail, but the system never fails.) There are two main problems with distributed systems: a) Designing and implementing them correctly is really hard. b) Many people use distributed systems when a single VM would do just fine, and get all the pain without cashing out on the benefits. See also http://idlewords.com/talks/website_obesity.htm#heavyclouds http://idlewords.com/talks/website_obesity.htm#heavyclouds
4) Continuous integration was not meant to help with complexity. Its purpose is to reduce turn-around time for bugfixes and new features. If your release process is long and complicated, the increased number of releases will indeed be painful for you. Our team sees value in "bringing the pain forward" in this way. Your team obviously puts emphasis on different issues, and that's okay.
- UK-AL 10y agoI find microservices can help in just keep everything small and focused. I know you can do this with a monolith. But having a process boundary really enforces it.
- Oras 10y agountil you mix it with other legacy part of the system then it will be pain in the neck
- crdoconnor 10y agoI find that the boundary creates operational headaches. A function call won't time out, deliver a 502 error, have authentication/authorization issues, require load balancing, etc. etc. A REST API will. Plus, once you've debugged a problem that involves crossing 5 microservice boundaries you'll start to wonder if it was all worth it. Monolith is also a wrong (and somewhat derogatory) word to describe a non-microservice architecture. There's nothing monolithic about loosely coupled code running on the same machine. I really think that microservices are a hack to deal with conway's law in large corporations. Operationally it's inefficient but it fixes a nexus of technical and political problems when the correct boundary is picked.
- misha67 10y agoWell said. "Monolith" is a pejorative that prejudices any discussion of said code.
- UK-AL 10y agoExcept most applications are monolith. Monolith code can still be loosely coupled. However it is harder.
- crdoconnor 10y agoNo, not at all. The only difference I noticed with respect to rube goldberg (what you call "microservices") systems and coupling is that tight coupling between components of rube goldberg systems was much more painful: particularly debugging across multiple service boundaries.
- user5994461 10y ago> 3) Depends. If you have a well-designed distributed system, it can be amazingly resilient and reliable without introducing much administrative overhead. About that points. Scaling developments across many devs is a very difficult problems. It just doesn't scale. A lot of organizations recruit/grow a lot of people and they try to get away from the human scaling problem by having them work independently/in their corner. This allows people execute a lot of stuff... usually the same stuff 10 times, with little coordination or collaboration between them to the point it can be felt it in the resulting system(s).