|
I don't work at Amazon, and haven't for a long time, and this format is insufficient to fully express what they're doing, so I won't try. You're better off searching for how Brazil and Apollo work. That being said, the short of it is that: imagine when you push a new revision to source control, you (you) can run jobs testing every potential consumer of that new revision. As in, you push libx-1.1.2 and anyone consuming libx >= 1.1 (or any variety of filters) is identified. If the tests succeed, you can update their dependencies on your package and even deploy them, safely and gradually, to production without involving the downstream teams at all. If they don't, you can choose your own adventure: pin them, fork, fix them, patch the package, revise the versioning, whatever you want. It's designed to be extremely safe and put power in the hands of those updating dependencies to do so safely within reason. Imagine you work on a library and you can test your PR against every consumers. It's not unlike what Google and other monorepos accomplish but it's quite different also. You can have many live versions simultaneously. You don't have to slog it out and patch all the dependents -- maybe you should, but you have plenty of options. It all feels very simple. I'm glossing over a lot. |