OK so not just me--this reads so poorly trying to suss out anything meaningful, especially from a technical standpoint. Or perhaps to the wishy-minded, reads very well.
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.
lost interest once I read the gartner quote. Not interested in punch lines and sales quotes...articles/publications by gartner are good reads when having number 2s only...and I tend to forget about just like what I flushed down if you get my meaning
5 comments
[ 3.0 ms ] story [ 26.9 ms ] threadAs 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.