Hacker News new | ask | show | jobs
by erik_seaberg 2370 days ago
I agree that gradual adoption of new APIs is the way to go, but once you're doing that you no longer need an atomic commit across all projects.
1 comments

You actually never want an atomic commit for that class of changes across projects because HEAD should always be deployable to all services. It's obviously messier at FAANG-scale, but with even 25 devs, not properly staging API-breaking changes leads to a lot of "only deploy commits before xxxx to service foo."