I see Enterprise Service Bus (ESB) and Service Oriented Architecture (SOA) has been rebranded. As with ESB's/Document/Event driven systems, even if you don't h

I see Enterprise Service Bus (ESB) and Service Oriented Architecture (SOA) has been rebranded. As with ESB's/Document/Event driven systems, even if you don't have an explicit Schema, you still have an implicit one. Be very careful to understand it and work to understand on how to make your data backward/forward compatible with systems reading that event stream. Not knowing WHO/WHAT is consuming events and what data/schema they require basically pours cement over the entire design locking you into a frozen design or forcing you to constantly break things. I assume/wonder (haven't worked in such a company) if this is why some larger companies end up with mono-repos because they have no other way to manage backwards data/schema compatibility on ESB systems.