3 ms·
Why can't you decouple teams form each other with modularity and encapsulation? I never worked in a team, but I could imagine that teams just have some agreemen
by vbezhenar 7y ago
Why can't you decouple teams form each other with modularity and encapsulation? I never worked in a team, but I could imagine that teams just have some agreements about interfaces and then work independently on a single code base but in a different classes and packages.
- yawaramin 7y agoBecause modules in the same codebase have an unfortunate tendency to cross each others' boundaries. It's just too easy for them to reach into each others' implementation classes and couple together strongly. But if they're different codebases, there's a stronger wall between them.
- mkleczek 7y ago(Micro)services and separate codebases are orthogonal. You can have multiple separate components (libraries) implemented in different codebases and linked as a single executable (which is actually really common). You can have (micro)services deployed from as single huge codebase - just take a look at all so-called monorepos.