Learn Backend Development Part-Time, Online
Learn AI, Data Science & Business — Earn Certificates That Get You Hired
Overview
Google, IBM & Meta Certificates – 40% Off
One Coursera Plus subscription covers most Professional Certificates on Coursera.
Unlock All Certificates
This talk explains how API builders can identify changes that may break consumer integrations, help consumers build more resilient integrations, and release risky changes safely. It covers documenting edge cases, semantic versioning, contacting affected integrators, and mitigation.
Syllabus
Introduction
A sad story
Examples
Definition
Assumptions
Observer behaviour
MSDOS example
Assumptions are unconscious
Document edge cases
Naming
A change isnt breaking
Not all breaking changes are equal
Identifying which integrators to reach out to
Semantic versioning
Overcommunicating
Mitigation
Conclusion
Taught by
Ruby Central