Corezoid Task — GitCall Node Round Trip

Corezoid Task — GitCall Node Round Trip A sequence diagram generated by Archify. POST /api/2/json create publish api_create_task consume shard S publish gitcall-v2 deliver op invoke user code result JSON publish reply correlated reply merge + persist task task result 200 JSON ops[] Intake GitCall execution Persist + reply API Client · REST caller · Sequence participant API Client REST caller conveyor_api · Cowboy :8080 · Sequence participant conveyor_api Cowboy :8080 RabbitMQ · vhost /conveyor · Sequence participant RabbitMQ vhost /conveyor worker · shard S · Sequence participant worker shard S GitCall · orchestrator · Sequence participant GitCall orchestrator Runner Pod · js / python · Sequence participant Runner Pod js / python PostgreSQL · cp_S · Sequence participant PostgreSQL cp_S Legend request return default message

Why two AMQP hops

  • • The worker never calls GitCall synchronously
  • • Dispatch and reply are separate exchanges

Correlation

  • • Task parks in a wait-tab ETS on dispatch
  • • Reply matched by correlation_id, not ordering

Latency shape

  • • Caller latency spans the conveyor_api activation
  • • Runner cold start dominates first-call time