Replication

Learn how Bunny Database separates storage from compute and replicates data across regions for low-latency access.

Bunny Database separates data storage (at rest) from data processing (in compute instances). This separation allows compute resources to be allocated dynamically in different regions while keeping data safely stored in its designated location.

Configure regions from the Dashboard or the Bunny CLI:

Dashboard

Manage regions from Dashboard > Edge Platform > Database > [Select Database] > Regions.

CLI

List, add, and remove regions with the bunny db regions commands:

bunny db regions list                 # show primary and replica regions
bunny db regions add --primary DE      # add a primary region
bunny db regions add --replicas UK,NY  # add replica regions
bunny db regions remove --replicas UK  # remove a region

At least one primary region must remain. See bunny db for the full command reference.

Storage location

Data can be stored at rest in:

• Toronto, CA (North America)
• Frankfurt, DE (Europe)

If a database doesn’t receive any requests, it will be moved to object storage and removed from all active regions to optimize costs.

Enabled regions

Replication regions

Replication regions function as dynamically provisioned read replicas, offering fast, low-latency data access while proxying write operations to the primary region.

Primary regions

The primary region handles write operations. You can select multiple regions, but only one is active at a time. The active primary region is automatically chosen based on latency. If a database becomes idle, the primary region may change when it’s reactivated.