4 ms·
>I've talked to developers who have taken a single app that worked perfectly fine and split it into five or six services just because "microservices!" I think
by superuser2 11y ago
>I've talked to developers who have taken a single app that worked perfectly fine and split it into five or six services just because "microservices!"
I think the idea is to use microservices when they will be owned by separate teams. If your application is small enough that a single team can meaningfully work on it, then you probably don't need to break it up.
- EdSharkey 11y agoCould you explain that to my manager please? He wants our one team to maintain 6+ microservices, each in their own git repo. Its going to be such a cluster-schtuppe, I just know it, and no one cares to listen to reason...
- deleted 11y ago[deleted]
- andrewchambers 11y agoSplitting your code becomes a pain when branches touch more than one program.