3 ms·
Enjoyed the article, and found #11 and #12 to be almost a requirement for most teams. I've worked for an org that adopted microservices when it's small size di
by muh_gradle 4y ago
Enjoyed the article, and found #11 and #12 to be almost a requirement for most teams.
I've worked for an org that adopted microservices when it's small size didn't justify it but eventually found its footing with good containerization, K8s from a growing DevOps team. Individual teams were able to eventually deploy and release to various environments independently, test on QA environments easily.
And I now work for an org with a monorepo with 100+ developers that probably should have been broken up into microservices a while ago. Everything just feels broken and we're constantly running around wondering who broke what build when. We have like 6 SREs for a team of 100+ devs? I think a lot depends on how well CI/CD is developed and the DevOps/SRE team.
- aliswe 4y ago> And I now work for an org with a monorepo with 100+ developers that probably should have been broken up into microservices a while ago. If its a monolith, then I think its not a monorepo?