Continuous Integration Strategies for APIs
APIs are increasingly becoming an integral part of applications, particularly in distributed systems architectures like microservices. Subtle but breaking changes can disrupt other teams or, for platforms, cause wide disruption among 3rd party integrations.
Further, a good API requires a high degree of stylistic and semantic consistency which can be hard to enforce across multiple teams.
This session introduces tools and techniques to tackle both of these challenges.
In this session, we introduce a strategy for API-first design that provides fast feedback for development teams, alerting them immediately when breaking changes are introduced. Likewise we will introduce API auditing and linting strategies to provide pipeline feedback on API designs.
Although this aspect of API governance is often missing from CI/CD pipelines, we'll show it's an easy incremental enhancement to add.
About Michael Carducci
Michael Carducci spent years learning to see things as they actually are; first as a magician, then as a software architect, now as both simultaneously. And somehow that’s not even the whole story.
He’s the author of Mastering Software Architecture (Apress, 2025) and is currently writing The Semantic Layer. He has spent over 25 years following interesting problems; through roles from individual contributor to CTO and back again, across industries and continents.
As a speaker, he applies the same toolkit he uses in close-up magic: attention, misdirection, timing, storytelling, and the instinct to take the long way around when that’s where the truth lives. Audiences at hundreds of conferences across four continents have described his talks as the kind that change how you think about a problem rather than just what you know about it.
He also makes YouTube videos about technology and curiosity with his wife Kate, because some ideas are too important (or too interesting!) to leave only in conference rooms.
More About Michael »