Safe high-frequency delivery and APIs that evolve without breaking consumers
Day 1
CI/CD Patterns — Progressive Delivery & Trunk-Based Development
- Trunk-based development: short-lived branches, commit frequency, feature flags as the enabler for trunk-based work
- Feature flags: LaunchDarkly, Flagsmith, and OpenFeature — flag types, lifecycle management, stale flag cleanup
- Canary releases: traffic splitting with Argo Rollouts or Flagger, automated canary analysis with Prometheus metrics
- Blue-green deployments: instantaneous cutover, rollback strategies, database migration compatibility
- Rollback strategies: fast-forward vs revert commits, feature flag kill switches, database backward compatibility
- Delivery metrics: deployment frequency, lead time for change, change failure rate, MTTR — measuring pipeline health
- Pipeline observability: tracing pipeline runs, alerting on pipeline failures, build time regression detection
Day 2
API Engineering — Design, Versioning & Contract Testing
- OpenAPI 3.1 spec-first workflow: designing APIs before implementation, code generation from spec, documentation automation
- Versioning strategies: URI path versioning (/v1/), header versioning (Accept), content negotiation — trade-offs
- Breaking vs non-breaking changes: additive changes, field removal impact, type widening vs narrowing rules
- Contract testing with Pact: consumer-driven contracts, Pact Broker for contract sharing, provider verification in CI
- API gateway patterns: rate limiting algorithms (token bucket, leaky bucket), authentication delegation, request/response transformation
- API lifecycle management: deprecation notices, sunset headers, versioning sunset policies, changelog communication
- CI integration: lint OpenAPI specs in CI, breaking change detection with oasdiff, contract verification on every PR
What your team walks away with
Participants can design delivery pipelines that ship safely at high frequency and APIs that evolve gracefully — combining progressive delivery techniques with automated contract enforcement.
- Design delivery pipelines for high-frequency shipping using trunk-based development and feature flag infrastructure
- Implement canary and blue-green deployments with automated rollback based on error rate metrics
- Design APIs that evolve without breaking consumers using spec-first OpenAPI 3.1 workflows
- Enforce consumer-driven contracts between services automatically in CI using Pact
- Detect breaking API changes before merge using automated spec diffing and linting in pull requests
Book the CI/CD + API Engineering training
Reach out to schedule a session for your team — remote, on-site, or hybrid, in German or English.
Get in touch