Skip to content
AntFabric Corev1.0.0local

Transports

From → to Transport Carries
App → API HTTPS/REST, /api/v1 Every read and write; JSON envelope { statusCode, status, message, data }
App ↔ API Socket.IO, /events Live events (server → app), subscriptions, presence, typing
App → object storage HTTPS PUT/GET on signed links File bytes; never through the API
API ↔ API replicas Redis (Socket.IO adapter) Socket fan-out, presence
Core service ↔ plugin In process (scoped SDK services) Everything a plugin asks of core
Plugin → plugin In process (contract registry) Contract calls, as the signed-in person
API → workers PostgreSQL outbox → Temporal Workflow starts
Workers → apps Event outbox → socket gateway Live events from background work
API / workers → people SMTP, Expo push, Web Push; inbox Notifications
Phone and desktop → API Same REST and socket Plus X-AntFabric-Client-Version for update checks
App Manager → instance Container runtime; signed recovery codes Provisioning, emergency access
  • Clients talk to the API and to signed storage links only. No client talks to Postgres, Redis, Temporal or another client.
  • Inside the API, everything is in process. A plugin calling core or another plugin is a method call, not a network hop.
  • Anything that outlives a request goes to Temporal, started through the outbox.
  • Events carry ids or small payloads; the app reloads what it shows through REST, which applies the access rules again.
  • Every request has a trace id, reused from X-Trace-Id or created, returned in the response and in error bodies, and carried into events, workflow starts and notifications.