API Gateway Platform  ·  View 09 of 21  ·  Data

Data Flow

Configuration flows down and evidence flows up. Nothing flows the other way on a request.

Editable source SVG draw.io All views
Authored Route definition reviewed in CI Plan and product limits, scopes Credential created portal Committed Config version N immutable, signed Verifier written no secret stored Distributed Snapshot published object store Proxies pull 99% in 10 s Version reported per instance Applied Resident snapshot in-process Per-request decisions no network hop Observed Access record ~1 KB, sampled RED metrics per route / tier Auth + config events never sampled Landed Analytics store 2 TB/day Metric store 13 months Audit ledger immutable Used Developer analytics 30 days Rollout scoring canary verdict Billing rollup daily revert to N-1 coverage Data Flow — Configuration Down, Evidence Up Application we own Security / platform Data store Decision point Queue / topic External / third party failure / alternate event / async The only upward arrow on the request path is evidence. Configuration never travels up, and a request never waits on anything on this diagram except its own upstream. v 1.0 · owner Integration Platform Architecture · date 2026-09

Decisions

  • Configuration becomes an immutable, signed version before it is distributed, so distribution is a content-addressed pull rather than a mutation (ADR-02).
  • Every proxy reports the config version it is actually running. Coverage is a measured number, which is what makes the 10 s propagation SLO falsifiable.
  • Billing is derived from access records, never from rate-limit counters — counters are approximate by design (ADR-06).

Numbers

  • Config change visible in ≥ 99% of instances within 10 s, 100% within 60 s (assumption).
  • Usage pipeline RPO ≤ 60 s; access records 90 days, aggregated metrics 13 months, audit 7 years (assumptions).

Risks

  • A fleet split across two config versions for longer than 60 s is a correctness problem, not a lag problem: two callers can get two different answers to the same request. It is alerted on (view 18).
◀  Integration Surface All views Data Architecture and Ownership  ▶
Solution Architecture v1.0 · Google Cloud · Integration Platform Architecture · 2026-09 · 21 views · 18 architecture decision records09-data-flow