SPARKPILOT ARCHITECTURE
AWS deployment map

How SparkPilot works

Follow the request through the system.

SparkPilot system flow

Click a component to inspect its connections or data.

Source and scope

Record values illustrate the implementation. Playback makes no application or AWS requests.

Learning order

  1. Requirements: customer compute, governed execution, investigation and evaluation. Tenant isolation and recovery.
  2. Entities: Tenant, Environment, Job, JobVersion, Run, ProvisioningOperation and conversation turn.
  3. Interfaces: request, response and state changes for each flow.
  4. Architecture: draw the UI, API, database, queues, workers and customer EMR. Trace a result back to the UI.
  5. Deep dives: delegation, durable dispatch, agent permissions and evaluation evidence.

Hello Interview’s public delivery framework.