World: Monoliths suck. Later: Monoliths are fiiiine but not at Google or Facebook scale. Megacorps: We love our monorepos!
Boundaries are well defined but people are expected to make cross repo changes when they change a leaf, which happens plenty.
-
-
If you're saying "people write modular software in practice", I would hope so or at Google scale they would explode.
-
But "monolith" never had anything to do with anti modular practices in the first place
-
Sure, the default is to change everything at once, usually a good thing, but you could release a beta of 1 pkg and adopt incrementally
-
Module boundary, package boundary, process boundary, server boundary, availability zone boundary. These are all options.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.