Asynchronous API
Versioning of our asynchronous APIs is concerned with the backwards compatibility of the event type definitions. Upstream components must uphold their contract with downstream components. Meanwhile, downstream components may need to support legacy event type definitions. Fortunately, event type definitions are only used within the cloud-native system and not exposed to third parties. This means that reasonable changes can be enacted relatively quickly with timely team coordination.
The event type names are the critical link that enables downstream components to consume the proper events. Therefore, it is important not to change the names of the event types. This is analogous to changing the endpoint of a synchronous API in ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access