AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service that's designed for your most demanding workloads, including hybrid transactional and analytical processing (HTAP). AlloyDB pairs a Google-built database engine with a cloud-based, multi-node architecture to deliver enterprise-grade performance, reliability, and availability.
AlloyDB automates administrative tasks, such as backups, replication, patching, and capacity management. AlloyDB also uses adaptive algorithms and machine learning for PostgreSQL vacuum management, storage and memory management, data tiering, and analytics acceleration. AlloyDB provides fast transactional processing, more than 4 times faster than standard PostgreSQL for transactional workloads. It's suitable for demanding enterprise workloads, including workloads that require high transaction throughput, large data sizes, or multiple read replicas. AlloyDB provides high-availability and an 99.99% uptime SLA, inclusive of maintenance. AlloyDB also provides real-time business insights and is up to 100 times faster than standard PostgreSQL for analytical queries. Built-in integration with Vertex AI, Google's artificial intelligence platform, lets you call machine learning models.
Nodes and instances
A cluster contains several nodes, which are virtual machine instances that are dedicated to running the PostgreSQL-compatible database engine that applications use to query your cluster's data. AlloyDB organizes nodes into instances, each of which has a private, static IP address in your VPC. In practice, your applications connect to instances at these IP addresses using PostgreSQL protocols. The instances then pass SQL queries to their nodes.
AlloyDB has two kinds of instances:
Primary instance: Every cluster has one primary instance, providing a read or write access point to your data. A primary instance can be either highly available (HA) or basic. HA primary instance: An HA primary instance has two nodes: an active node and a standby node. AlloyDB monitors the availability of the active node, and it automatically promotes the standby node into the active node when necessary. Basic instance: Non-production environments not requiring high availability can optionally use basic instances. A basic instance has only one node, with no standby node. For more information, see . Read pool instance: Your cluster can optionally have one or more read pool instances, each containing one or more read-only nodes, up to a cluster-wide maximum of 20. AlloyDB automatically load-balances all requests sent to a read pool instance, routing them to the instance's nodes.