To start using AlloyDB Omni, you first need to choose one of the following deployment environments:
- AlloyDB Omni for Kubernetes
- AlloyDB Omni for containers
AlloyDB Omni for Kubernetes
Choose AlloyDB Omni for Kubernetes if you need one or more of the following capabilities. To start using this deployment model, see AlloyDB Omni for Kubernetes overview.
- Automated provisioning and API-driven lifecycle management.
- Configurable high availability to fine tune failover mechanisms.
- Sidecar support for integrating enterprise backup or monitoring agents.
- Variable read pools for scaling read-only operations.
- Load balancing with server-side connection pooling (PgBouncer).
- Platform support and marketplace availability for Google Distributed Cloud and OpenShift.
- Cross-region disaster recovery to create standby databases in remote clusters, data centers, and regions.
AlloyDB Omni for containers
Choose AlloyDB Omni for containers if you need one or more of the following. To start using this deployment model, see AlloyDB Omni for containers overview.
- Single application database: when you need a high-performance database dedicated to a single application.
- Development and testing: for setting up a database environment on a developer's laptop or in a testing environment.
- Non-Kubernetes environments: when your infrastructure doesn't use Kubernetes or when you don't need the complexity of a container orchestrator.
- Offline operations: for applications that must continue to function even when they are disconnected from the internet.
- Low-latency requirements: when you need to place the database geographically close to your users to ensure the fastest possible response times.