2 ms·

Atomic commits are a red herring because deployment isn’t atomic or irreversible. You still have to think about how the system stays healthy while a new build i

Atomic commits are a red herring because deployment isn’t atomic or irreversible. You still have to think about how the system stays healthy while a new build is halfway deployed. A deprecated API still needs to work until you’re certain you will never roll back any consumer and start calling it again.

rav 6y ago
At least with a monorepo you only have to worry about deploy ordering. With a multirepo you have to worry about code review and merge order before you get to worry about the deploy order. I would like to be able to review the library API change together with the changes in the app that need the new API. At my work we either review library changes in isolation, or we skip the review on library changes (if the author deems them trivial) and only do review on the main app changes, but that means we often miss opportunities for making the library API fit the use-cases as well as they could.