Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(architecture): point the SQLite note at MAX_CONCURRENT_SESSIONS

Yudhi Armyndharis97fc91eb7e2d
diff --git a/docs/03-system-architecture.md b/docs/03-system-architecture.md
index 6eb527e6e..f7fc28485 100644
--- a/docs/03-system-architecture.md
+++ b/docs/03-system-architecture.md
@@ -1427,9 +1427,10 @@ return {
> **Note:** OpenWA does not currently apply SQLite-specific concurrency hardening. There is **no**
> `journal_mode = WAL` PRAGMA, no `SqliteWriteQueueService`, and no application-level write
-> serialization or session cap in the source. SQLite is used with TypeORM's defaults, so its standard
+> serialization in the source. SQLite is used with TypeORM's defaults, so its standard
> single-writer behavior applies. For high write-concurrency or multi-session deployments, use
-> PostgreSQL (`DATABASE_TYPE=postgres`). Cross-dialect schema differences are handled at migration
+> PostgreSQL (`DATABASE_TYPE=postgres`). `MAX_CONCURRENT_SESSIONS` (default `0`, unlimited) caps
+> concurrent sessions on any database. Cross-dialect schema differences are handled at migration
> time (see below), not by a runtime optimizations layer.
#### Migration Strategy