Applications

BigState connects your services into one live ecosystem. Each application can publish object state over HTTP and receive matching updates through delivery channels—so backends, browsers, and workers share the same versioned view of changing data.

Service A publishes state → BigState stores and routes → Service B / clients receive updates

What you get#

Low latency

Publish over HTTP and push matching updates to subscribers as soon as state changes.

High throughput

Support many concurrent publishers and subscribers across objects and deliveries.

Typical application flow#

  1. Create credentials for each service or environment (Account and credentials).
  2. Define objects for the streams you share (counters, locations, metrics, device readings).
  3. Publish state from trusted backends with the HTTP API or JavaScript client.
  4. Configure delivery so frontends and other services receive only the objects they need.
  5. Authorize with principals and policies so keys stay scoped per app.

Start building#

Related#

  • Use cases — where application state sharing fits
  • Humans — publish public states for people and apps
  • AI — feed agents and workflows from the same states
IntroductionHumans

© 2024 BigState