Notify subscribed applications when event contracts change to prevent consumer breakages

In event-driven systems, multiple teams often consume events from shared Kafka topics that are exposed through Event Endpoint Management. Over time, producers may evolve event schemas or update the event contract.

Evolving these contracts safely can be difficult because producers often do not know which applications depend on a topic. As a result, consumers sometimes discover breaking changes only after deployment.

As event-driven systems scale and the number of topics and consuming applications grows, manually communicating changes through email, documentation, or team coordination becomes difficult and unreliable.

Event Endpoint Management already provides visibility into which applications have subscribed to an event source. Building on this capability, topic owners could notify subscribed applications when an event contract changes.

Notifications could be delivered through mechanisms such as:

• Email notifications to registered subscribers
• Webhooks or callbacks that integrate with Slack, Microsoft Teams, or internal tooling
• An RSS or event feed that developers can subscribe to

This would help teams evolve event contracts more safely while maintaining trust between producers and consumers.

For example, if a producer removes or renames a field in an event schema, consumers may break without warning. This can easily happen in environments where multiple teams depend on the same shared event and changes cannot always be coordinated manually.

When teams are unsure how changes will impact consumers, they often take defensive approaches such as creating new topics or duplicate event definitions instead of evolving existing ones. Over time this can lead to unnecessary topic proliferation and a fragmented event catalog. A notification mechanism would allow teams to communicate these changes earlier and plan migrations safely.

This capability would benefit platform teams, integration teams, and application developers by improving visibility and coordination when evolving event contracts.

If you find this capability useful in your organization, please consider voting for this idea to help prioritize it.