From commit to cloud: Powering what’s next for PostgreSQL

PostgreSQL has go foundational to however modern applications are built. It powers everything from early‑stage startups to immoderate of the astir demanding accumulation systems successful the world. Its longevity isn’t accidental, it’s the effect of decades of engineering discipline, assemblage collaboration, and a relentless absorption connected correctness and extensibility.

PostgreSQL has go foundational to however modern applications are built. It powers everything from early‑stage startups to immoderate of the astir demanding accumulation systems successful the world. Its longevity isn’t accidental, it’s the effect of decades of engineering discipline, assemblage collaboration, and a relentless absorption connected correctness and extensibility.

As exertion architectures evolve, and arsenic AI becomes a default portion of the bundle stack, PostgreSQL continues to adapt. This adaptability is simply a cardinal crushed Microsoft has been investing profoundly successful PostgreSQL: 345 commits contributed to the latest PostgreSQL release, a squad of PostgreSQL committers and contributors moving straight connected the upstream project, and a increasing portfolio of managed services, developer tools, and community programs built astir Postgres connected Azure. Here’s what’s driving that investment, and what it means for the radical gathering connected Postgres today.

Figure 1: This infographic highlights the galore ways Microsoft contributes to and supports the PostgreSQL ecosystem

Why PostgreSQL, and wherefore present

Across industries, PostgreSQL is progressively the default choice for caller workloads and modernization projects. That displacement is driven by 3 wide trends.

1. PostgreSQL is trusted with existent accumulation systems

PostgreSQL earned its estimation by solving hard problems successful accumulation environments: transactional correctness, concurrency control, extensibility, and operational resilience. These characteristics weren’t designed for isolated benchmarks; they emerged done years of moving ngo captious systems nether existent pressure.

Microsoft runs PostgreSQL astatine planetary standard and sees these aforesaid patterns firsthand. Many upstream contributions, specified arsenic caller enactment successful PostgreSQL 18 connected asynchronous I/O, vacuum behavior, and query planning, are informed straight by accumulation bottlenecks encountered astatine scale.

This feedback loop works some ways. Improvements made upstream payment the full PostgreSQL ecosystem, portion lessons learned from large‑scale deployments proceed to pass aboriginal development.

2. Databases are becoming portion of the AI stack

Databases are nary longer isolated retention layers. In modern systems, they progressively beryllium wrong feedback loops that impact reasoning, ranking, and decision‑making.

Developers gathering AI‑enabled applications are asking caller questions:

• How adjacent tin vector information unrecorded to transactional data?
• How tin similarity hunt respect SQL predicates?
• How tin inference, ranking, and structured information enactment unneurotic without excessive glue code?

PostgreSQL’s extensibility makes it a earthy instauration for these patterns. That’s wherefore Azure Database for PostgreSQL and Azure HorizonDB absorption on integrating AI‑related capabilities, specified arsenic vector hunt and exemplary invocation, straight into acquainted PostgreSQL workflows.

3. Different workloads, antithetic paths to scale

As applications scale, not each workload benefits from the aforesaid architectural approach.

Some teams privation a afloat open, single‑node PostgreSQL acquisition with minimal abstraction. Others request elastic scale, multi‑zone replication, and accelerated failover but don’t privation to propulsion complexity into the exertion layer.

This diverseness is wherefore Microsoft supports aggregate PostgreSQL deployment models connected Azure:

• Azure Database for PostgreSQL for open‑source‑aligned workloads and lift‑and‑shift scenarios.
• Azure HorizonDB for cloud‑native systems that necessitate scale‑out compute, shared storage, and low‑latency planetary resilience.

These aren’t forks. They are antithetic engineering responses to antithetic workload realities.

Microsoft’s concern successful PostgreSQL goes beyond merchandise announcements for Azure’s managed services to see shipped codification from in-house contributors, upstream collaboration, and accumulation reliability. As our learnings expand, we’ve utilized these insights to enrich the open-source Postgres motor for the broader community.

Upstream contributions that payment everyone

Postgres committers and developers astatine Microsoft actively lend to the PostgreSQL unfastened root project, moving alongside the planetary assemblage connected halfway improvements. Recent mentation updates see contributions across:

• Asynchronous I/O foundations.
• Performance improvements successful vacuum and representation management.
• Planner and execution enhancements for ample datasets.

These changes onshore upstream first, ensuring that improvements are broadly disposable not tied to immoderate azygous unreality oregon service. A transparent overview of our Postgres enactment is published annually.

Architectural motivations down Azure HorizonDB

Azure HorizonDB was built to code a circumstantial people of PostgreSQL workloads that are constrained by azygous node scaling but not good served by exertion level sharding. For example, high-throughput, low-latency systems that necessitate horizontal standard without adding exertion complexity.

Key architectural goals shaped Azure HorizonDB:

• Independent scaling of compute and storage.
• Failover and betterment operations decoupled from information size.
• Multi‑zone replication enabled by default.

The effect is simply a PostgreSQL‑compatible work with a shared‑storage, scale‑out plan supporting sub‑millisecond multi‑zone commits and maturation to thousands of cores, without requiring exertion rewrites.

Azure HorizonDB extends PostgreSQL’s scope portion maintaining compatibility expectations that developers trust on.

Improving the developer acquisition wherever enactment really happens

PostgreSQL has agelong been a developer‑centric database. Tooling investments connected Azure bespeak that mindset.

With much than 500,000 installs, the Visual Studio Code hold for PostgreSQL brings provisioning, schema exploration, show diagnostics, and migration workflows directly into the IDE developers already use. Integrated GitHub Copilot assistance helps with SQL authoring, tuning, and adjacent analyzable migrations, specified arsenic Oracle to PostgreSQL, which is 1 of the astir challenging existent satellite scenarios teams face.

The hold helps to region unnecessary friction portion keeping PostgreSQL familiar.

Investing successful the PostgreSQL ecosystem

PostgreSQL’s advancement has ever depended connected its community. That’s wherefore Microsoft’s concern extends beyond products and services.

Microsoft sponsors and helps signifier PostgreSQL conferences and idiosyncratic groups worldwide including PGConf.dev, PGConf EU, PGConf India, and galore others. POSETTE: An Event for Postgres is simply a escaped and virtual Postgres lawsuit organized by the Postgres squad astatine Microsoft and successful concern with AMD. It covers a wide scope of topics including internals, ecosystem tools, existent satellite debugging stories, and accumulation architectures. This year’s 5^th yearly event, hosted 16-19 of June, brings unneurotic contributors, users, and engineers from crossed the Postgres assemblage to stock what works successful practice.

Talking Postgres, a monthly podcast that our squad produces, features conversations with radical who enactment with Postgres, from longtime contributors to accumulation engineers solving hard problems astatine scale.

And the Microsoft Blog for PostgreSQL provides regular heavy dives connected merchandise updates, migration guidance, and real-world Postgres usage patterns connected Azure.

Looking ahead

PostgreSQL is approaching its 4th decennary and it’s inactive accelerating. What began arsenic a probe task astatine UC Berkeley, is present a wide utilized database for modern applications, from developer experiments to mission-critical accumulation environments.

As the assemblage celebrates this moment, Microsoft’s absorption remains consistent:

• Strengthening PostgreSQL halfway done upstream collaboration.
• Extending PostgreSQL responsibly for AI‑driven and cloud‑native workloads.
• Preserving developer spot done unfastened standards and transparency.

These priorities signifier ongoing investments successful Azure Database for PostgreSQL, Azure HorizonDB, developer tooling, and assemblage engagement. Updates crossed these areas are present shared regularly done the Microsoft for PostgreSQL LinkedIn page.

A wide takeaway

PostgreSQL’s success has ever been rooted successful engineering subject and assemblage trust. Sustaining that occurrence requires meaningful, long‑term investment, not conscionable successful services, but successful the task itself and the radical down it.

Microsoft’s committedness to PostgreSQL reflects that belief: contributing upstream, gathering thoughtfully, and supporting an ecosystem that continues to determination the database forward.