3 ms·

Don't make breaking API changes, you can't deploy them atomically. You have to support the old API until everyone has safely migrated and confirmed no rollback

Don't make breaking API changes, you can't deploy them atomically. You have to support the old API until everyone has safely migrated and confirmed no rollback will be needed.

joshuamorton 6y ago
There are more apis than just rpc ones. If I change my library's api, I can update the callers atomically.
fsociety 6y ago
Then services would be stuck in a sea of technical debt. There are too many moving pieces to do that.
- erik_seaberg 6y ago
  Technical debt is a tool to be used (with caution). Getting ludicrously far behind is a risk I'd avoid, but our stability is more important than staying on the bleeding edge and testing every single version of each of our dependencies.
djohnston 6y ago
you can if it's a monorepo and all your callers are in the monorepo, which sort of answers OP's question
- erik_seaberg 6y ago
  The commit can be atomic, but if prod is many machines, the deployment cannot.