Lost in translation - Data vs Integration Architecture

We communicate daily. It’s easy if we use the same language, work in the same context. The reality is, we really don’t - we live in different contexts and use different languages even if we all speak English - our internal dictionaries, mental models and jargon differ.

We communicate daily. It’s easy if we use the same language, work in the same context. The reality is, we really don’t - we live in different contexts and use different languages even if we all speak English - our internal dictionaries, mental models and jargon differ.

Jargons differ, especially at work. We would like to have cohesive languages to communicate with between all lines of business, all units, departments, etc. The facts are that we don’t have them, we all assume we understand the same terms the same way, and that creates a lot of friction and confrontation.

The same applies to architecture fields - and this is very visible when we compare Data and Integration Architecture and how specialists in those fields communicate with each other. Best example, a Loosely Coupled episode we did in August last year (https://www.youtube.com/watch?v=JaCuv8gRnJg), where we had so much trouble with understanding the terms we used.

This episode we’ll dive back into the topic of Data and Integration Architectures and try to find where we have mismatches! Hopefully we can create a common dictionary translating between the two worlds! To help us in the endeavor, joining as a guest is Andrew Jones! Returning to the stream to have yet another lost in translation moment.

Join us in the discussion! Post your terms in advance! Let’s see how many mismatches we can find and solve!