← All thinking

Your platforms can talk, but does your business actually work as one?

Integration vs connectivity: why "the systems talk" is the wrong test, and what a governed event contract actually proves.

Integration By a Senior Solution Architect

How data flows through a connected estate: systems of record for orders, customers and content publish governed events onto an event backbone with a schema registry; consumers process them idempotently, with failed messages quarantined in a dead-letter queue and replayed; a continuous stream and a nightly batch feed a lakehouse serving BI and an AI assistant; identity and an API gateway govern every call.HOW THE DATA FLOWSIDENTITY · SSO / OIDC ON EVERY CALLAPI GATEWAY · SYNC ACCESSCDCERPorder.postedSoR · orders & GLCRMcustomer.updatedSoR · customerCMScontent.publishedSoR · contentEvent backboneschema registry · governed contractsDLQquarantine · replayPersonalisationconsumes & publishesNotificationsidempotentSearch indexrebuilt by replayANALYTICS PLANELakehouseraw → modelledBI dashboardssemantic layerAI assistantRAG + live reads
A connected estate is a set of deliberate decisions: which system owns each entity, what contract its events keep, and where a failed message goes instead of vanishing. The same governed flows feed the lakehouse, so BI and AI read the truth the business runs on.

Making two systems talk is a week of work: a webhook, a nightly sync, a point-to-point call. Making a business run as one, across everything it depends on, is a different problem, and it’s the one most integration projects quietly leave unsolved.

”Integrated” is a low bar

Integration is a technical fact: data moves from A to B. You can demo it by Friday. What a demo doesn’t test is whether both sides agree on what the data means once it lands. Point-to-point integrations rarely share a canonical definition of “customer” or “order”: three systems, three slightly different truths, patched over by a nightly reconciliation job.

The mechanism: a contract, not just a pipe

Connectivity starts with a decision most integrations skip: which system is the system of record for each entity, and what the event contract leaving it promises. Get that right and consumers can be built idempotent, safe to replay without double-processing. Skip it and every new integration adds another undocumented special case to a web nobody can reason about six months later.

Every new expectation (faster service, AI reading live data) lands on this layer first, and a governed contract is the difference between adding a consumer in an afternoon and a three-month project to renegotiate what a field means everywhere it’s read. Two systems that talk isn’t proof of anything. A contract that survives a new consumer and a schema change is.

More thinking

See the work
02

How do you build a connected core without a leap of faith?

What a connected core changes for your business, and the staged path that gets you there without a blind commitment.
03

Can a packaged product carry your business model, or only most of it?

The real platform question is whether a product fits your business model. If it does not, or you are not sure, a proper buy-vs-build evaluation decides, not a forced fit.

Let’s start something that lasts.

Bring the problem you’re weighing: a migration, a re-platform, a build that has to hold. You’ll talk to the people who’d do the work, not a sales desk.

Book a meeting

Let’s talk

Book a meeting

A 30-minute video call with the people who’d actually do the work. Pick a time, tell us what you’re weighing, and we’ll bring the right minds, not a sales desk.

  1. Date
  2. Time
  3. Reason
  4. You

Which day works?

Times shown in your timezone.

Pick a time

What’s it about?

Last thing — who are you?