Choose your AlloyDB Omni deployment option

To start using AlloyDB Omni, first choose the deployment option that best meets your infrastructure needs. The available options are containers, Kubernetes, Red Hat RPM orchestrator, and RPM standalone. To help you choose, this page explains recommended use cases for each available deployment option and provides links to more information.

AlloyDB Omni for containers

Choose AlloyDB Omni for containers if you need one or more of the following. For more information, 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 achieve the fastest possible response times.

To start using AlloyDB Omni for containers, see Plan your installation and Install AlloyDB Omni for containers.

AlloyDB Omni for Kubernetes

Choose AlloyDB Omni for Kubernetes if you need one or more of the following capabilities. For more information, 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.

To start using AlloyDB Omni for Kubernetes, see AlloyDB Omni availability reference architecture and Install AlloyDB Omni for Kubernetes.

Red Hat RPM orchestrator

Preview

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

For information about access to this release, see the access request page.

Choose the Red Hat RPM orchestrator deployment option if your organization has significant investments in virtual machine (VM) infrastructure and established operational practices built around tools like Ansible. For more information, see the Red Hat RPM orchestrator deployment overview.

Common use cases include the following:

• Enterprises with VM infrastructure: supports companies where Kubernetes isn't standard, or environments with strict security postures, regulatory requirements, or application dependencies that prefer standard VM deployments.
• Simplified operations: automates database deployment, configuration, and lifecycle management using familiar tools, for example, Ansible.
• High availability and disaster recovery: sets up resilient AlloyDB Omni clusters with automated failover and recovery mechanisms.
• Hybrid environments: provides consistent database operations across on-premises data centers and cloud VMs.
• Legacy system integration: integrates with existing applications and systems designed for non-containerized environments.

To start using the Red Hat RPM orchestrator deployment options, see Install the AlloyDB Omni orchestrator.

AlloyDB Omni for Linux

Preview

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

For information about access to this release, see the access request page.

Choose AlloyDB Omni for Linux if you have an environment where containerization isn't preferred or where deep integration with the host operating system is required. For more information, see AlloyDB Omni for Linux overview.

Common use cases include the following:

• Modernizing legacy applications: upgrade existing PostgreSQL workloads running on Linux servers to AlloyDB Omni for Linux to gain performance and manageability improvements without replatforming to containers.
• Edge computing: deploy high-performance databases in remote data centers where resource constraints or operational models favor direct operating system (OS) installation.
• Development and testing: give developers a powerful, local database instance that mirrors the production AlloyDB for PostgreSQL environment, enabling consistent testing and rapid iteration.
• Regulated environments: run workloads in strictly controlled environments where using container runtimes might be restricted by security policies.

To start using this Preview deployment model, sign up to request access.

For more information, see Plan your installation and Install AlloyDB Omni for Linux.