4 ms·
I always thought microservices were an organizational solution to the problem of bloated headcount on teams meeting the hard reality that if you put more than t
by thrower123 6y ago
I always thought microservices were an organizational solution to the problem of bloated headcount on teams meeting the hard reality that if you put more than two cooks in the kitchen, diminishing and counterproductive results are the norm.
- linkdd 6y agoTeam oriented architecture? I worked in some companies where each team were managing multiple micro services. Micro services answer a very specific problematic: they are small to allow the least technical debt per "business features". The less technical debt there is, the more robust your system is against changing specs.
- candiddevmike 6y agoWhat is your definition of technical debt here? Just because something has a small LOC, doesn't mean it lacks tech debt. It's just harder to find and quantify. In fact, I would posit they're littered with tech debt, especially from an infrastructure and shared services standpoint.
- linkdd 6y agoServices should be independent of each others (as much as possible). IMHO, technical debt is found in coupling (modules, services, ...), the number of dependencies (not only code dependencies, since making an HTTP request also introduces a soft dependency), and the amount of knowledge required to understand the code. If your service is unaware of its infrastructure (understand: i don't care if i run in docker/k8s/baremetal/...), the infrastructure's technical debt does not leak to the code.