PostgreSQL Hyperscale
It began with an acquisition.
Best in class
With the acquisition of Citus Data, Microsoft procured the leading PaaS offering for PostgreSQL scale out. It also inherited a remote team of brilliant engineers and some complexity.
While coming in-house, Citus continues to have a passionate community fan base, and a competing presence on AWS.
Additionally, Citus came with a design and UI language that needed to be adapted to fit within the Microsoft and Azure brand languages and UX patterns.
Two systems become one
Alignment between Citus and Microsoft wasn’t fraught with insurmountable challenges, but working within the Azure Portal framework did present a need to change the way some settings were represented. It also required that the newest OSS offering on the block fit in comfortably with it’s peers.
We adopted a card pattern that I piloted for Azure SQL, but adapted it to allow for a little more information required to differentiate Hyperscale from it’s single server siblings.
Feature expansion & hybrid data
Networking updates across they entire family of services were driven initially by new requirements that having a multi-node instance required. Additional configuration options on top of those already present continue to pop up.
The latest is the ability to deploy PostgreSQL Hyperscale server groups into your existing Kubernetes infrastructure via Azure Arc enabled PostgreSQL Hyperscale.
