Overview
DocsDatabasesDatabases overview

Databases overview

Every managed database on StackBlaze can run as a single Standard instance or as a replicated, high-availability deployment. Pick the topology per database when you create it.

Standard vs high availability

Each database add-on supports two deployment topologies. You choose between them when you create the instance (and you can scale up later by raising the replica count).

Standard deployment is a single database pod with one volume. High-availability deployment is a primary plus replicas spread across nodes, fronted by a service, with streaming replication and automatic failover.
Standard runs one instance and one volume. HA runs a primary plus replicas across nodes, with automatic failover.

Standard

A single instance with its own persistent volume. It is the simplest and lowest-cost option, and it is a good fit for development, internal tools, and workloads that can tolerate a short restart during maintenance or a node move. There is no automatic failover: if the pod or its node is rescheduled, the database is briefly unavailable until it comes back.

High availability (HA)

A clustered deployment with a primary plus one or more replicas spread across different nodes. Writes go to the primary and stream to the replicas; if the primary fails, the cluster promotes a replica automatically so the database stays available. HA also lets you serve reads from replicas to take load off the primary. It uses more resources, so it is the right choice for production and anything with an uptime requirement.

StandardHigh availability
InstancesSinglePrimary + 1 or more replicas
Node spreadOne nodeReplicas on separate nodes
FailoverNone (restart)Automatic primary promotion
Read scalingPrimary onlyReads can fan out to replicas
Best forDev, internal, non-criticalProduction, uptime SLAs

Choosing a topology

Start Standard for development and switch to HA before you carry production traffic. For most engines you raise the replica or node count and StackBlaze performs a rolling change with no data loss.

Available databases

StackBlaze provisions each database through a Kubernetes operator, so the same engine you run locally runs in your cluster with backups, private networking, and zero-config connection strings. The table below lists every managed database and the topologies it supports.

Relational (SQL)

DatabaseEngineTopologies
PostgreSQLCloudNativePGStandard + HA
MySQLMariaDB (MySQL-compatible)Standard + HA
CockroachDBDistributed SQLStandard + HA

Key-value & cache

DatabaseEngineTopologies
RedisValkey (Redis-compatible)Standard + HA
MemcachedMemcachedStandard only

Document

DatabaseEngineTopologies
MongoDBDocumentDB (MongoDB-compatible)Standard + HA
CouchDBApache CouchDBStandard + HA

Search & vector

DatabaseEngineTopologies
OpenSearchOpenSearchStandard + HA
MilvusMilvus (vector DB)Standard + HA

Analytics

DatabaseEngineTopologies
ClickHouseClickHouseStandard + HA

Wide-column

DatabaseEngineTopologies
CassandraApache CassandraStandard + HA
ScyllaDBScyllaDB (Cassandra-compatible)Standard + HA

One engine, the names you know

Some databases are served by a compatible engine so we can ship them under a permissive license without changing your client code. MongoDB is provided by DocumentDB (MongoDB wire protocol), Redis by Valkey, and MySQL by MariaDB. Your existing drivers, connection strings, and tools work unchanged.

See Backups & recovery for the backup and point-in-time-recovery behavior that applies across every database.

Looking for messaging? Kafka and RabbitMQ are documented under Messaging.