Concern about tenant separation being out of scope.
Goal of RFC was to reduce the partition count and therefore reduce costs
Tenant separation seems to be another large issue and too much scope for this RFC
Original per-tenant Kafka messages at least allowed us to keep
Temporary Kafka security solutionwould be rendered obsolete/deprecated by this RFC (though it seems unlikely this will be done any time soon)
Does theALL tenant topic would close the door to the possibility of separating tenant messages?
RFC describes an option to combine tenant message, not a requirement
Major trade-off is that we are committing in the long term to support two fundamentally different approaches for the foreseeable future, but does keep the door open
RFC is intended to be practical was of addressing pain points, which includes limited development and funding; hurdle is very high to implement enhanced security
Other notes?
Inference: providers do not migrate all tenants to new flower releases all at once, and therefore need multiple versions of a module are active at once. This gives a scenario where multiple versions of Inventory will be consuming a message.