Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

Capacity and reliability

This page lists practical scaling and reliability considerations.

Scaling dimensions​

ComponentScales with
APIrequest rate, payload size, auth verification cost
workerswebhook volume, background jobs, aggregation workload
Postgreswrite rate (events, commits, ledger), read rate (catalog, reports)

Reliability practices​

  • Use bounded retries and stable idempotency keys.
  • Monitor rate limiting and treat sustained 429 as a capacity signal.
  • Keep Postgres connection pooling and limits tuned to avoid saturation.
  • Prefer incremental rollout and canaries for application changes.

Next​