Parent: #12
Today: hardcoded SQLite with one global connection. To run several bridges behind a load balancer (or for HA), need a shared backend — Redis or Postgres being the obvious candidates.
Touch surface: define Storage protocol; refactor every db() call site in server.py (~12) to go through it; new storage/ subpackage with SQLiteStorage (default), RedisStorage, PostgresStorage. ~400 LoC.
Tradeoff: adds dependency surface and config complexity. Don't pursue unless multi-instance deployment is a real ask. Biggest architecture lift on the roadmap.
Effort: L.
Status: deferred-pending-demand.
Parent: #12
Today: hardcoded SQLite with one global connection. To run several bridges behind a load balancer (or for HA), need a shared backend — Redis or Postgres being the obvious candidates.
Touch surface: define
Storageprotocol; refactor everydb()call site inserver.py(~12) to go through it; newstorage/subpackage withSQLiteStorage(default),RedisStorage,PostgresStorage. ~400 LoC.Tradeoff: adds dependency surface and config complexity. Don't pursue unless multi-instance deployment is a real ask. Biggest architecture lift on the roadmap.
Effort: L.
Status: deferred-pending-demand.