What happens if a PropExecutor server goes down?
Quick answer
The backend is designed to run as more than one instance behind a load balancer, with a reconciler keeping each instance's view of positions, orders and balances consistent with the database every 10 seconds. Write paths are safe across instances, and the service shuts down gracefully, finishing in-flight requests before stopping.
Detailed answer
Reliability is built into how the backend handles state.
Multiple instances
Each instance runs its own price feed and keeps an in-memory index of open positions for speed. Instances stay consistent through:
- Idempotent writes: closing a position or settling an order succeeds once, even if two instances try.
- A reconciler: re-reading positions, orders and balances from the database every 10 seconds.
Database as the record
Trades, positions and account status are stored in PostgreSQL. In-memory data is a fast copy, rebuilt from the database.
Graceful shutdown
On a restart, an instance stops accepting new requests, completes the ones in progress, and flushes background work before exiting.
Rule decisions
Breaches are written to the database when they happen; a periodic safety-net reload keeps in-memory rule state aligned.
What this does not promise
PropExecutor does not publish an uptime percentage. If an outage affects your traders, your firm's outage policy decides how affected accounts are treated; breach times in each account's record show which accounts were affected.
PropExecutor team · Updated
Related questions
All 11 questions in Security, data and reliability · Every category