Building Platforms For Vendor-Led Enterprises
Why customers whose integration work is delivered by external vendors need a platform, not more governance meetings, to stop quality drifting away the moment the vendor leaves.
Most of what I write about comes back to the same problem: organisations know what good API design and integration architecture look like, but knowing it and enforcing it are two different things. This is the collection of articles where I dig into that gap — automating governance instead of documenting it, using OpenAPI and its surrounding tooling (Arazzo, Overlay) to make the right path the easy path, and building platforms that hold up even when the people doing the integration work aren't your own employees.
Why customers whose integration work is delivered by external vendors need a platform, not more governance meetings, to stop quality drifting away the moment the vendor leaves.
Azure API Management can now publish directly to Service Bus with a native policy, cutting the Function or Logic App you used to need just to bridge sync and async traffic.
Every engagement eventually produces the same question from management. A maturity model turns it from a matter of opinion into something you can point at.
A practical example of using Overlay Specification to automate your API governance. All with the goal of ensuring consistently applying predicatable changes to API descriptions.
A practical example of using linting tooling to automate your API governance. Free developers from having to remember each individual convention and design rule by automating the process.
OpenAPI version 4 codenamed Moonwalk is scheduled in development. I'll be covering everything you need to know about this new major version.
Arazzo is a new open-source project that aims to improve developer experience by providing a specification for workflows using OpenAPI. In this article, we will explore the key features and benefits of Arazzo, and how it can help developers create better workflows in their applications.