Integration architecture

For twenty years my job has been to make systems that were never meant to talk to each other work as one. That means knowing the old world — IBM Integration Bus, API Connect, point-to-point ETL — well enough to retire it safely, and the new one — event-driven, API-led, domain-oriented — well enough to put it into production.

What I do

• Modernisation paths that don't break the business. Moving from batch and point-to-point integration toward streaming and APIs, incrementally, with the legacy estate still running.
• Standards that scale across teams. REST design, API lifecycle and versioning, OpenAPI contracts, and the governance to make them stick when twenty teams are involved.
• Contracts at the seams. Schema governance and data contracts where domains meet, so a change on one side doesn't silently break the other.

Evidenced by

• Cloud Gateway — twenty-plus fragmented gateways consolidated into one federated, cross-cloud, self-service platform handling ~500M+ requests a month.
• Confluent Kafka data-product platform — domain-oriented streaming across 30+ source systems with governed schemas.

Background: 20+ years across SOA, ESB modernisation and API management; Accenture Certified Technology Architect; TOGAF 9.