Choose a single-server application connection ​

The documented Coordinator DB server workflow lets several clients connect to one server process using native TCP or HTTP. It does not require a separately configured coordination service for that local service.

Choose one persistent database owner process and route application requests through its public interfaces. Several connections in that process can share the file. Separate processes must not open the same database file simultaneously; pointing independent services at a shared path does not create a supported cluster.

If you need a separate instance for testing or recovery, create an independent database copy with VACUUM INTO, then open it with its own listener addresses. That copy is independent. It does not replicate later source writes or elect a replacement server automatically.

Applications that need failover, replicated data or multi-region behavior must first distinguish those requirements from the available single-server connection model. Do not add coordination configuration fields that are absent from the public server reference and expect them to change the file-sharing rules.

Verify connectivity and recovery using the documented procedures before exposing the service to callers.

See deployment modes, native connections, HTTP and independent copies.