3 ms·
> microservices are primarily for team scaling I've never heard this before or thought about it this way. If you need to restructure your code because of your
by smt88 8y ago
> microservices are primarily for team scaling
I've never heard this before or thought about it this way. If you need to restructure your code because of your team size, you have a bigger problem with your code than whether it's separated into microservices or not.
"Let's do everything as microservices" seems like a trend from a few years ago that has now somewhat died down. My suspicion is that it was PaaS companies like Heroku pushing people to do this because it made more sense for their products, but I don't have any evidence for that.
Since then, it seems that people have remembered not to solve a problem you don't have. If your code works and it's easy enough to work on it, you don't need to radically change its structure.
Keep in mind that several companies have tens of thousands of employees working on a mono-repo.
> I'm curious to see if there's a clear cut off which dictates that...
There's no clear cut off for anything in managing a software team. It's not a science, and individual situations vary too much to create hard and fast rules.
- drbojingle 8y agoThanks, I appreciate your feedback! > There's no clear cut off for anything in managing a software team. It's not a science, and individual situations vary too much to create hard and fast rules. Intuitively, I disagree. There's a lot of nuance for sure but, but there are still patterns that can be noticed.
- smt88 8y agoThere may be patterns, but who says they're good patterns? I see more badly-run teams than well-run teams.
- drbojingle 8y agoOut of curiosity, from your perspective, is there anything that the bad teams share that the well run teams don't and vice versa?
- karmakaze 8y ago> If [...] easy enough to work on it, you don't need to radically change its structure. This is precisely the point. When you have a large number of developers all working on the same deployment unit, it isn't easy to work on. A mono-repo is orthogonal to microservices.
- scirocco 8y agoAnd being difficult to work on means dependencies with other teams, making changes slow. This slows down innovation speed and enables competitors to launch competing services faster. So there's the business need of microservices :)
- closeparen 8y agoMonorepos and monoliths are completely separate concepts. There are monoliths that import hundreds of separately versioned components from separate repos. And there are monorepos from which hundreds of different services are deployed, which do not directly link against each other at all. Monorepos are about library versioning, not architecture.