Reactive Backend

Comparable to: Convex, Firebase, Supabase, Appwrite

Key Concepts

Use the concepts below when they fit the task. Not every reactive backend needs every trigger or realtime surface shown here.

• State is the "database" — CRUD via state::set, state::get, state::update, state::delete, state::list
• State triggers fire automatically when any value in a scope changes
• Side effects (notifications, metrics, stream pushes) are wired reactively, not imperatively
• Streams deliver real-time updates to connected clients

Architecture

HTTP CRUD endpoints
  → `state::set`, `state::update`, `state::delete` (writes to 'todos' scope)
    ↓ (automatic state triggers)