AlloyDB Omni using RPM overview

Select a documentation version:

To run high-performance database workloads directly on your own infrastructure without the overhead of containers, use the AlloyDB Omni Red Hat Package Manager (RPM) deployment option. This overview describes how to install and manage the AlloyDB for PostgreSQL engine on standard Linux distributions like RHEL 9 and Rocky Linux 9.

To get started with this deployment model, submit this form to request access.

Use cases

The RPM deployment option is designed for environments where containerization isn't preferred or where deep integration with the host operating system is required. Common use cases include the following:

  • Modernizing legacy applications: upgrade existing PostgreSQL workloads running on Linux servers to the RPM deployment option 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.
  • High database performance: experience high performance on bare metal or virtual environments.
  • Securing data at rest: secure all data at rest in your AlloyDB Omni clusters without modifying your application code by enabling transparent data encryption. By enabling this feature, you ensure that all critical data at rest is automatically encrypted before being written to disk. This helps you meet compliance requirements and protects sensitive information.

Benefits

AlloyDB Omni using RPM offers the following benefits:

  • Superior performance: it uses the AlloyDB for PostgreSQL columnar engine and intelligent caching to deliver faster analytical queries and higher transaction throughput compared to standard PostgreSQL.
  • Full control: it installs directly on the OS, giving system administrators complete control over resource allocation, file system configuration, and network settings using standard Linux tools.
  • 100% PostgreSQL compatibility: it is fully compatible with PostgreSQL, which lets you use existing tools, drivers, and extensions without code changes.
  • Operational simplicity: it integrates natively with RHEL systems. You can manage the database service using systemctl and install or update it using dnf, fitting seamlessly into existing Linux administration workflows.
  • Intelligent automation: it reduces administrative toil through autopilot features like adaptive autovacuum and automatic memory management, which dynamically adjusts the shared buffer cache based on system memory pressure to optimize resource usage without manual tuning.

Architecture

The RPM deployment option runs as a set of integrated software components directly on the host operating system. It uses the standard Linux file system for storage, letting you use your existing storage infrastructure and management practices.

Core components

The RPM deployment option architecture consists of the following primary RPM packages that work together to deliver the database service:

  • alloydbomni: this package is the core database engine. It contains the enhanced PostgreSQL server binaries, the AlloyDB for PostgreSQL columnar engine, and the autopilot management extensions. It runs as a system service (managed by systemd), handling client connections, query processing, and data storage.
  • alloydbomni_monitor: this package is a lightweight monitoring agent that runs alongside the core engine. It collects telemetry and performance metrics from the AlloyDB for PostgreSQL instance and exposes them over the Prometheus protocol for observability tools.

System integration

The RPM deployment option integrates directly with the Linux ecosystem:

  • Service management: the database runs as a systemd service (alloydbomni18.service). Administrators use standard commands, such as systemctl start, systemctl stop, and systemctl status, to manage the database lifecycle.
  • Package management: installation and updates are handled using the dnf package manager, which allows for straightforward version control and dependency management through standard repositories.
  • File system: data is stored in standard directories (for example, /var/lib/postgresql/), which enables the use of standard Linux backup tools and storage snapshots. However, you can configure a different directory for data storage.

What's next