Resources
Use cases, architecture guides and comparisons for teams running databases on Kubernetes with Solanica and OpenEverest.
Use cases
What teams run on Solanica.
- Database-as-a-ServiceA self-service database platform on your own Kubernetes clusters, in any cloud or data center, as an alternative to RDS.
- Internal Developer PlatformDatabases in your internal developer platform, provisioned through Terraform, Helm or Backstage.
- Databases for AI AgentsAn instant, disposable branch of production-sized PostgreSQL for every agent, CI job and pull request, with reset, rollback and promote.
- AI InfrastructureVector databases such as Milvus and Qdrant, and private LLMs, on your own infrastructure, with the data kept inside your network.
- Database AI CopilotalphaQuery tuning, debugging and index recommendations that you approve before they run. Your data stays in your network.
- SQL Server on KubernetesMicrosoft SQL Server on any Kubernetes cluster, with failover, backups and upgrades handled by the platform.
- OpenEverest on VMware vSpherePostgreSQL, MySQL and MongoDB on vSphere Kubernetes Service clusters, tested with Broadcom.
Whitepapers
Architecture guides for engineers running databases on Kubernetes.
- The Cloud-Native Data ManualAvailability, compute, storage, backups, cost and security for production databases on Kubernetes.
- Running PostgreSQL on KubernetesStreaming replication, Patroni failover, PgBouncer, pgBackRest backups with point-in-time recovery, and the operators.
- Running MySQL on KubernetesGroup Replication, Galera and semi-sync replication, XtraBackup with point-in-time recovery, and the operators.
- Running MongoDB on KubernetesReplica sets, sharded clusters, WiredTiger and oplog sizing, backups with point-in-time recovery, and the operators.
- Running SQL Server on KubernetesAvailability groups without a Windows cluster, licensing-aware sizing, native backups to S3, and the operators.
- Running Valkey on KubernetesReplication and Valkey Cluster, persistence, maxmemory and container limits, RDB and AOF, backups, and the operators.
Operator comparisons
Kubernetes operators for the same database, side by side.
- PostgreSQL operatorsPercona, CloudNativePG, Zalando and StackGres, compared on features, community health, business viability and day-2 operations.
- MySQL operatorsPercona XtraDB Cluster, Percona Server, Oracle and MOCO, compared on replication, high availability, backups, community health and day-2 operations.
Solanica and managed services
How running databases yourself with Solanica compares with a managed service, including where the service comes out ahead.
- Solanica vs Amazon RDSRDS runs PostgreSQL and MySQL for you, only on AWS. Solanica runs them on any Kubernetes cluster, with backups in open formats in your own bucket.
- Solanica vs AivenAiven runs your databases on its infrastructure. Solanica runs them on yours, in your own cloud account or data center.
- Solanica vs MongoDB AtlasAtlas runs MongoDB for you in MongoDB's cloud. Solanica runs it on Kubernetes you control, including on-premises and air-gapped.
- Solanica vs Azure SQL Managed InstanceManaged Instance runs SQL Server for you, only in Azure. Solanica runs it on Kubernetes you control, with backups as standard .bak files in your own bucket.