User can make sure only well-formed messages reach the broker without having to touch a single line of code

[fmvilas]

Description

When doing EDAs, there is a common problem that repeats across many companies, especially the big ones. People are not able to answer the question "who is subscribing to this topic/channel?". This management problem derives into a more serious one: someone makes a breaking change on the information sent on one channel and others break because they were not aware of this change. Hopefully, the subscribers break in a "noisy" way so you can detect the error and fix it. Other people opt for not pushing breaking changes into an existing channel and decide to create a new one, leading to a pile of unused channels over time.

The problem I just described actually consists of two parts:

1. Lack of discovery tools for EDAs. E.g., being able to answer the question "who is subscribing to this channel?"
2. Lack of management tools for EDAs. E.g., making sure only the right data gets into a channel.

This outcome is about the second part: "Lack of management tools for EDAs".

Scope

1. User is able to make sure only well-formed messages reach the broker.
2. It should not be needed to change a single line of code.
3. It works with the main protocols: HTTP, Kafka, AMQP 0-9-1, AMQP 1.0, WebSockets, MQTT, and MQTT5.