Real-Time Analytics Platform · View 17 of 21 · Operations

CI/CD and Environment Promotion

How a change reaches production, what stops a bad one at each gate, and how a streaming job is released without skipping an event.

Editable source SVG draw.io All views

The gates that matter

Schema compatibility gate — a breaking contract change cannot merge
Latency gate — a build that pushes end-to-end p95 past 5 seconds does not promote
Consumer contract tests run against the actual registered schema, not a fixture

Zero-downtime release

Blue/green uses a second consumer group starting from the same committed offsets
Green is verified against shadow output before blue is stopped, so no event is skipped
Materialized view rebuilds run behind the serving alias; readers see no downtime

Rollback

Auto rollback triggers on consumer lag breach within the 48-hour watch window
Rollback is a consumer-group switch, not a redeploy, so it completes in under two minutes
Any data written by green during the window is corrected by the replay path

◀ Deployment and Infrastructure All views Observability and Service Level Objectives ▶