PostgreSQL continues to consolidate its position as a selection of the highest database level between workload running on Kubernetes.
In the constantly developing world of cloud technologies, PostgreSQL continues to consolidate its position as the highest database selection between workload running on Kubernetes. According to Kubernetes in the Wild 2025 reportPostgreSQL now strengthens 36% of all databases that run on Kubernetes – up to 6 points from 2022 – signal its growing popularity and growing confidence between Kubernetes community1. However, starting the postgreSQL work load on Kubernetes has its own challenge set. These include the Kubernetes Primitive Administration, such as status and deployment, as well as achieving optimal configuration performance by setting up storage, replication and database, but this is rapidly evolving to a simplified experience.
Now we provide two options for deploying StatEFUL PostgreSQL workload based on performance needs. To support the databases with strict latency and scalable transactions, you can use the Azure containers storage for orchestration of Kubernetes to place the NVMe to extend the IOPS while maintaining an extremely low Latence Sub-MS. For scenarios where optimized performance is priority, the premium SSD V2 is the choice. In addition, we integrated with CloudNatePg to the robust operator Open-source for PostgreSQL, which supports a high-avilabibility database on Azure Kubernetes (AKS). Our advanced storage possibilities combined with cloudNatePg makes AKS a robust platform for high -performance workload PostgreSQL.
Breakthrough power PostgreSQL with local NVMe
For PostgreSQL working loads in critical performance such as those dealing with massive competitive transactions or demanding access to low latency, access to low latency, Local nvme Your best bet is directly connected to Azure Virtual Machine (VM) SKU. The use of local NVMe disks with Kubernetes used to be complicated – it is often necessary to set RAIDs across discs and manual management of static volume orchestrators. Azure container storage effectively solves this challenge.
Azure containers storage It is a fully managed solution for storage on the container, designed specifically for Kubernetes. Developers can easily apply for a bundle of Kubernetes and Azure will dynamically provide storage supported by available local Discs on NVMe nodes. This provides users PostgreSQL direct connection of block storage and latency within the managed orchestrated cloud environment. Whether you supply payment systems, gamends or real -time personalization engines, you get the best of speed and simplicity. It also supports Azure containers storage Azure disk and Elastic SanSo you can choose the accompanying storage with different durability, scale or cost, as your needs are evolving-under the word, Kubernetes-Nantive control plane.
The results of Oourchark showed that PostgreSQL reached almost 15,000 transactions per second (TPS) with a single-digit millisecond latency of the end-to-end with standard_L16S_V3 VM. When we expanded to the width of VM SKU, such as standard_l64s_v3, we observed TPS reaching up to 26,000 While holding low latency. For more information about our benchmark runs Fer do Comparison of the Storage Options Section Below.
Optimize the price-output with premium SSD V2
Azure Premium SSD V2It offers an optimal balance with price performance and a flexible deployment model, which makes it particularly good for production that needs to be scaled over time. With the premium SSD V2, you can configure IOPS, permeability and size – allow PostgreSQL to be deployed for dynamically scaling with a request and minimize initial costs and prevent sources.
Whether you are a more tenant operating the SAAS platform, a production system that expands with business needs or the application with pointed operations, this flexibility leads to Actual savings without sacrifice . With 80 000 IOPS and 1 200 MB/s Premium SSD V2 Highly demanding workload PostgreSQL for infrastructure that adapts your application is the premium SSD V2.
Comparison of storage options
To help you assess the two storage options, conductive reference runs using the cloudepg operator settings to AKS with a similar core and memory consumption, with both storage options as the only variable: one using the local NVME WIT Premium SSD V2 with DISK CSI.
For the first configuration, we used Standard_D16D_V5 SKU and provided two premium SSD V2 32 GIBs, each with 3000 IOP and 125 MB/s for log and data files. In the second setting, we ran to Standard_L16S_V3 knots with local NVMe storage. The test environment was configured to closely simulate the real world database scenario. TPS measures how many individual transactions (such as inserting, updating, removal or select) can process the system per second. Latence concerns a time delay between imitating the database request and receiving a response that is particularly critical to applications requiring real -time response or almost real time, such as financial systems, online gaming or high -performance analysis.
Local NVMe on Standard_L16S_V3 delivered 14 812 TPSwith Average latency 4,321 milliseconds. PremiumV2_Lrs to record standard_D16DS_V5 8 600 TPS at 7,417 milliseconds. See Price Comparison below:
*Monthly costs are based on 3000 IOPS and 125 MB/with permeability. You can add power (capacity, permeability and IOPS) at any time the SSD V2 premium discs, allowing the workload to be cost -effective if the workload size and performance requirements are met.
** With 3 VM VM L16S_V3, you get a 11.52 TB of storage by default, which is used to feed the volume created for PostgreSQL workload. For other VM sizes in the L series, the price per month and the assigned storage varies.
For PostgreSQL workload, the selection between local NVME and premium SSD V2 depends on the balance of performance, cost and durability. Local NVMe through Azure Container Storage offers extremely low latency and high permeability, which implies to post -stressful performance sensitive. The costs are higher for local NVMe and there is less flexibility for scale independent of the workload characteristics. The premium SSD V2 provides better price efficiency and flexible scalabibility, making it a viable option for PostgreSQL instances that require manipulation with increased scale or application that have an unpredictable increase in demand or use. In terms of data durability, the Premium SSD V2 offers local redundancy by default, while the local NVMe is recommended to use an architecture based on replica managed by the CloudNatePg operator and backup based on objects to prevent data loss.
Built for high availability with cloudNativePg on Azure Kubernets service
For teams deploying PostgreSQL in production, High availability and backup are non -aims. With Open-Mource CloudNatePG operator, a highly available postgreSQL cluster can be easily deployed with:
- Assembly Replication and automated service takeover in failure.
- The application lies Backup with native integration with Azure Blob storage.
- Trouble -free integration with Azure containers storage.
- Flexible storage options: Premium SSD V2 or Local NVMe for workload needs .
Whether you support internal business applications or customer platforms, it gives you Peace of mind Without problems with the logic of high availability and separate backup workflows. Start with the deployment of highly available PostgreSQL on AKS with the operator CloudnativePg using our reference manual step by step.
Prepared for the future
PostgreSQL is just one of the many state workloads that the organization now runs on Azure Kubernetes Service. FROM databaseon Tails of the news,, By an inference of AIand Business applicationsAKS develops to meet the needs of persistent and data applications in production.
Whatever you put on Repeat,, Mongudb,, Kafka or evenPipeline serving mlWith Nodes supported by the GPU, the AKS provides the Foundation for Management of these Work Stress with performance, consistency and operating ease, along with net lead tond guidance.
With innovations such as Azure containers for local NVMe and premium SSD V2 for scalable, persistent storage, we facilitate status applications that are: reliable, efficient and cost -effective for critical workload.
Modernize the data layer today at Kubernetes. When PostgreSQL or any Azure status level, it brings performance and manageability to make it happen. Explore verified patterns and deployment options in the AKS StateFul Workware report.
1Kubernetes in the Wild 2025 report