World: Monoliths suck. Later: Monoliths are fiiiine but not at Google or Facebook scale. Megacorps: We love our monorepos!
-
-
-
Replying to @mamadero
A monorepo is a setup where all dependencies across the whole company are revved in lockstep. Sure sounds like what ppl hate abt Monoliths.
2 replies 0 retweets 1 like -
Replying to @wycats
On a well implemented monorepo boundaries between packages are well defined. Also lockstep is the default, but optional.
1 reply 0 retweets 0 likes -
Replying to @mamadero
Boundaries are well defined but people are expected to make cross repo changes when they change a leaf, which happens plenty.
1 reply 0 retweets 0 likes -
If you're saying "people write modular software in practice", I would hope so or at Google scale they would explode.
1 reply 0 retweets 0 likes -
But "monolith" never had anything to do with anti modular practices in the first place
3 replies 0 retweets 1 like -
Replying to @wycats
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
1 reply 0 retweets 0 likes
Module boundary, package boundary, process boundary, server boundary, availability zone boundary. These are all options.
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.