Governance01
API governance without the bureaucracy
A few rules checked automatically at deployment time are worth more than a committee: a pragmatic approach to API governance.
Read the noteTHE CAB INGÉNIERIE TECHNICAL NOTEBOOK
Start with a question.
See it in practice.
APIs, integration, security. Documented experiments to understand what works, what gets in the way and what still needs checking.
Explore the notes08published notes
FROM THE NOTEBOOKAPI & INTEGRATION
Change the gateway. Keep the contract.
How do you prepare an API migration without disruption? Take inventory, run both gateways, then move traffic progressively.
Read the noteEXPERIMENTS & FIELD NOTES
Have a question in mind?
Start with the topic that interests you. Each note explains an approach, its observations and its limits.
8 notes shown
GitOps02
Versioning APIs in Git: what belongs in the repository, and what should never go there
Repository structure, per-environment values, secrets kept out of Git: the concrete choices that make Git the source of truth for your APIs.
Read the noteAPI & integration03
Leaving a proprietary API gateway without breaking contracts
Inventory of contracts, coexistence of gateways, gradual cutover, rollback: a method for migrating an API gateway without disruption.
Read the noteIdentity04
Zero-downtime OAuth2 rotation: the overlap strategy
Rotating client secrets and signing keys without interrupting the service: two values valid in parallel, a cutover, then withdrawal.
Read the noteSecurity05
Keeping secrets out of API pipelines with a vault
Secrets read at runtime, federated CI identity, least privilege, named traceability: getting secrets out of API deployment pipelines.
Read the noteSovereignty06
Sovereignty of integration flows: knowing where your data goes
Map your API and integration flows, identify dependencies outside the EU and document your choices: a concrete approach, without promises.
Read the noteAPI & integration07
webMethods 10.15: pitfalls of the administration REST API (and how to work around them)
Wrapped responses, nested policy bodies, encoded aliases, 200s that do nothing: a field guide to automating API Gateway 10.15.
Read the noteGitOps08
Deploying webMethods APIs in CI with Jenkins, Ansible and GitLab
A webMethods API deployment chain driven by Git: the role of each tool, the pipeline steps, the checks and the rollback.
Read the noteNo notes match this search.
THE LABS APPROACH
Show the path.
Make the limits clear.
A useful note goes beyond the conclusion: it gives you enough context to understand how we got there.
Set the context
The problem, the assumptions and what we want to understand.
Try it in practice
The scenario, conditions and steps behind the reasoning.
Look at the facts
Observed results, available evidence and differences.
Know how far to go
What the experiment supports — and what it has not demonstrated yet.
TAKE IT FURTHER
From notes to resources.
CONTACT
A question worth
putting to the test?
Let’s talk about a technical question or explore how it applies to your context.
Write to Christophe
Looking for hands-on support?
Explore CAB Ingénierie ↗