We do not need it at that moment, but in future we will need to provide a way for messages to confirm their origin. Currently, any service can give any origin identity. It could be a security risk or event or even unintended error when two services provide events with the same tag. It could probably be solved by a special security manager service and an additional field for security fingerprint.
We do not need it at that moment, but in future we will need to provide a way for messages to confirm their origin. Currently, any service can give any origin identity. It could be a security risk or event or even unintended error when two services provide events with the same tag. It could probably be solved by a special security manager service and an additional field for security fingerprint.