Request Flow & Data Lifecycle

Request lifecycle (end-to-end)

Acceso keeps request behavior consistent across domains. That consistency is what makes automation safe.

This is the one-page mental model. For the step-by-step gateway breakdown, see Request Lifecycle.

1

1) Client sends a request

  • REST call or SDK method call.

  • API key is provided in the request.

2

2) Gateway enforces safety

  • Authenticates the key.

  • Enforces quotas and rate limits.

  • Validates and sanitizes parameters.

  • Creates a request identifier for tracing.

3

3) Gateway routes to a domain service

  • Routing is version-aware.

  • Each domain service has bounded responsibility.

4

4) Service resolves data (cache → upstream → derived)

  • Reads from Redis when safe.

  • Falls back to upstream providers when needed.

  • Builds derived views when the request demands analytics.

5

5) Service normalizes and enriches

  • Parses raw protocol formats.

  • Normalizes schemas to a stable contract.

  • Applies enrichment (labels, computed fields, aggregates) when applicable.

6

6) Response returns through the gateway

  • Errors are standardized.

  • Telemetry is emitted (latency, status, upstream health signals).

  • The response is delivered to the client.

Acceso turns upstream data into normalized, reusable primitives. Those primitives then power multiple products (REST, streams, webhooks, SDKs).

Data lifecycle (what happens to raw inputs)

  1. Ingest raw data from upstream sources (RPCs, protocol APIs, vendors).

  2. Parse into internal representations (instruction decoding, adapters).

  3. Normalize into stable schemas (consistent naming and typing).

  4. Enrich with derived fields and context (when safe and deterministic).

  5. Cache normalized payloads or derived views based on volatility.

  6. Deliver via request/response or event-driven channels.

Cache entries should store normalized payloads. This avoids serving different shapes from different upstream vendors.

Delivery surface choices

Pick REST vs streams vs webhooks based on freshness needs:

Freshness and delivery choices

PreviousHigh-Level System OverviewNextPlatform Evolution Strategy

Last updated