3 ms·
Totally agree. Micro services unnecessarily makes thing complicated for small teams. IMHO it solves the problem of velocity ONLY when a large engineering team i
by abhisek 1y ago
Totally agree. Micro services unnecessarily makes thing complicated for small teams. IMHO it solves the problem of velocity ONLY when a large engineering team is slowed down due to too much release & cross cutting dependencies on a monolith. Although I see people solving with modular monoliths, merge queues and CODEOWNERS effectively.
Few cases where microservices makes sense probably when we have a small and well bounded use-case like webhooks management, notifications or may be read scaling on some master dataset
- mamidon 1y agoCan you elaborate a bit on codeowners, I've not heard of that kind of solution before.
- Jemaclus 1y agoThey're a way to assign ownership to individuals or teams on a granular basis, rather than at the repo-level. You can assign entire folders or individual files to people. Here's more at Github's docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners https://docs.github.com/en/repositories/managing-your-reposi...
- mithametacs 1y agoYou just put a text file with the names of the team or developers who own the directory.