6 ms·
Even more than the efficiency penalties, it's the drastic increase in complexity that makes me want to stay far, far away from microservice architectures.
by musicale 6y ago
Even more than the efficiency penalties, it's the drastic increase in complexity that makes me want to stay far, far away from microservice architectures.
- gonzo41 6y agoLike all legacy tech. Wrap it in a box of tests don't touch it and just manage the risk down over 20 years. Just like migrating away from a mainframe.
- yaml-ops-guy 6y agoAm I doing myself a disservice by actively avoiding shops that want to go down the k8s road? Asking in interviews questions like “how many namespaces are you managing or expecting to manage” and often times teams are talking about a single microservice and bringing in k8s “just in case” To which I’ve oft said “good luck in your endeavors”
- goodoldneon 6y agoK8s solves a specific set of problems that mid- to large-sized companies face. If the company is big enough to have multiple K8s experts then it can be successful
- jjav 6y ago> Am I doing myself a disservice by actively avoiding shops that want to go down the k8s road? From the resume-driven-development angle, probably. I do the same though. If you prefer to work in a sane environment though, wise choice.
- mathgladiator 6y agok8s sits on a list of things that I hope to avoid long enough before I can retire.
- kbenson 6y agoI felt largely the same way, but now our company has enough microservices that without something like k8s it's hard to actually sufficiently test anything well. Sure, we have test setups for any one service, and tests for that service with some other services mocked, but there's really no way to spin up a real full dev or QA environment with all the services interacting without herculean effort, and keeping it up to date would be non-trivial. I still haven't done anything with k8s, but I suspect it's the solution to this problem, even if it would take that same herculean effort to finally get everything moved to using it (we don't even run containers, we run our own application delivery system that has some similarities without the process isolation, because we've been doing so since before Docker existed).
- jjav 6y ago> I felt largely the same way, but now our company has enough microservices that without something like k8s it's hard to actually sufficiently test anything well. That feels like a self-inflicted wound that will now only get worse with k8s.
- kbenson 6y ago> That feels like a self-inflicted wound What's the alternative? It's not like we're some web property with an application, it's an ISP, and we sell internet services, and we've been around long enough that we still offer traditional ISP services (many for free) such as email, hosting, VPN service, etc, as well as telecom services. These often need to communicate with each other in some way, as well as many back-end services we've written to serve our staff. Microservices come with problems, but honestly I can't see a large monolithic app (or even a few of them) being much better development wise, even if it might have been easier to test and set up a development environment.
- jeltz 6y agoAs someone who has also tried to avoid it but now failed: it is not all bad, but it is immature, opionated in weird ways and make some normally simple problems very hard. The advantages is that it in return makes some hard problems trivial. So far I would not say it is worth it for most people. I also hate how much the community just runs random shit from the internet without any strategy for security patches or digital signatures.
- nostrebored 6y agoWell designed microservices drastically reduce complexity and mental overhead of working with a system. The problem is companies with poorly designed monoliths hit complexity problems more quickly and often. If software architecture is not a core competency, solutions architecture is probably not either, and poorly designed microservices are a completely different beast. A distributed monolith is inherently more difficult to maintain and operate.
- bildung 6y agoBut why would the same people that poorly designed the monolith be able to design the intrinsically more complex microservice architecture better?
- mkoubaa 6y ago+1 We have to keep in mind that not all software systems are designed by savants, and even ones that are might be constrained by business needs from rearchitecting them when they need it
- nostrebored 6y agoThat's what I was trying to articulate in the end. Microservices are generally less complex.They can appear more complicated because companies who are choosing to transition usually do so after a problem. These problems are often due to poor monolith design. Teams that design poor monoliths typically have neither a software or solutions architecture proficiency
- spaetzleesser 6y agoMy simple rule is: if you can’t write a decent library you won’t be able to write a well designed microservice. Microservices have all the challenges of library design plus quite a few more.
- jjav 6y ago> microservices drastically reduce complexity and mental overhead of working with a system If you only need to understand and maintain one of them, sure. That would be extremely rare though. You have to understand the entire system and all the interaction between all the parts. At which point the 10x complexity of excessive microservices will kill you.