Prematurely of Ignite, I spoke to Shireesh Thota, CVP Databases at Microsoft, concerning the new service. He described the rationale for a brand new PostgreSQL variant:
I believe more and more what we discover is that individuals both go into the bucket of, “I need to carry and shift my PostgreSQL that’s working in the neighborhood model on-premises, or possibly one other cloud.” They need to transfer it to Azure. They need 100% Postgres. They need all extensions working. They simply need one thing that actually has the flexibleness of efficiency and pace. Then Azure Database for PostgreSQL, the present model is ideal. Anyone who needs to construct an AI-native, cloud-native type of a workload that will want a variety of storage, needs actually quick latencies, considerably larger IOPS. You then go to HorizonDB.
Definitely, the revealed efficiency knowledge for Azure HorizonDB is spectacular: Microsoft is claiming a three-times improve in throughput over the open supply launch when working transactional workloads. You’ll be able to scale as much as 3072 cores, with 128TB of storage and sub-millisecond commits. HorizonDB builds on Azure’s multiregion structure with knowledge replicated in a number of availability zones and automatic upkeep and backups with minimal impression on operations. Such efficiency is required for AI functions and for large-scale Kubernetes. As Thota notes, “These cloud-native workloads can actually succeed on HorizonDB.”
Key to the efficiency enhance are modifications to the structure of the database, separating compute and storage and permitting them to scale independently. In the event you want extra compute, Horizon DB will give it to you. In the event you want extra learn replicas, it’ll provision them.
