# Scaling and High Availability

EventSourcingDB **does not currently support horizontal scaling or high availability**. This includes:

- Running **multiple database instances** concurrently
- **Clustering** or **leader election**
- **Automated failover** or **replication**

These features are planned for a **future release**.

> **Current Limitations**
>
> EventSourcingDB currently operates as a **single-instance system**. Running multiple instances against the same data directory **is not yet supported** and **may lead to data corruption or undefined behavior**.

Until built-in support is available, use the following strategies to **ensure resilience**:

- Deploy EventSourcingDB on **stable infrastructure with reliable storage**
- **Use automated restarts** (e.g., via `--restart always` in Docker)
- Apply backup and restore strategies to **protect against data loss**
- Use network-level isolation to **prevent conflicting deployments**

Once native support for high availability is available, **this page will be updated** with configuration details and deployment patterns.