DATABASE MODERNISATION

How a PostgreSQL Estate Became Manageable Without Starting Over

A staged adoption story for teams with valuable databases, uneven automation and no appetite for a risky rebuild.

The estate had grown the way successful estates often do: one important database at a time. Each instance worked, each DBA knew its history, and almost none of that knowledge was encoded in a repeatable operating path.

Start with one workload | Scale into a complete platform | Open Source Freedom | Enterprise-Grade Operations.

Published | June 2026

A platform already in motion

The estate had grown the way successful estates often do: one important database at a time. Each instance worked, each DBA knew its history, and almost none of that knowledge was encoded in a repeatable operating path.

A clean-room rebuild would have created more risk than it removed. The organisation needed to discover what existed, transfer management deliberately, and preserve database authority throughout the transition.

The turning point

The journey was split into three visible stages: discover without mutation, adopt configuration and service ownership, then modernise backup, monitoring and lifecycle controls behind explicit gates.

The team used OSS Manager to make policy-driven PostgreSQL deployment and operations reviewable and repeatable. The engine still owned its native behaviour; the control plane made intent, prerequisites, execution and evidence visible to the people responsible for the service.

What had to become explicit

• The service boundary: OSS Manager coordinates a primary and replicas, connection endpoint, backup and WAL archive, monitoring, security, and controlled maintenance while PostgreSQL remains authoritative for transaction semantics.
• The operational controls: major-version compatibility, replication and backup proof, role separation, extension inventory, configuration diff, service ownership, and application acceptance.
• The capacity conversation: database and index size, working set, transaction rate, connection concurrency, WAL rate, replica count, backup window, retention, and growth.
• The human boundary: who may observe, who may approve, who may execute, and who decides whether the application is ready.
  

The architecture that changed the conversation

The diagram is deliberately centred on the decision the team had to make. It is not a product inventory. It shows where authority sits, what crosses the boundary, and where a failed assumption must stop the workflow.

The practical design choices

These choices are intentionally small enough to review and test. They keep the architecture tied to operating behaviour instead of allowing a visually impressive diagram to hide unclear ownership.

What OSS Manager changed - and what it did not

OSS Manager brought discovery, planning, guarded execution and normalised status into one path for PostgreSQL. It did not replace the engine's correctness model or the application's responsibility for data semantics.

• Before change, validate versions, hosts, identities, artifacts, topology and the recovery boundary without mutating the service.
• During change, persist progress, expose stop conditions and prevent a partial result from being mistaken for success.
• After change, observe availability; replication lag; WAL growth; connection saturation; locks; slow queries; vacuum health; bloat; backup age; recovery readiness and run representative application journeys, not only process checks.
• For recovery, protect the last known-good authority and require an explicit decision before promotion, rollback or destructive cleanup.

The failure modes worth rehearsing

The test plan should make room for replica divergence, WAL archive gap, connection exhaustion, long transaction, blocked vacuum, missing extension library, backup failure, and accidental dual-primary risk. The purpose is not to produce a longer checklist. It is to learn whether operators can recognise the failure and choose the safe next action while the evidence is incomplete.

A human operating model

L1 operators need a plain-language answer to what is healthy, what is delayed and whether a change is in progress. Platform engineers need topology and evidence. Application owners need to know what users will experience. A useful platform connects those views without giving every person the same privileges.

Where this pattern earns its place

Retail

This pattern is relevant where teams need campaign peaks, catalogue freshness, transaction continuity and rapid rollback. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.

Telecom

This pattern is relevant where teams need high event volume, distributed operations, identity boundaries and service assurance. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.

Gaming

This pattern is relevant where teams need latency-sensitive sessions, leaderboards, event streams and regional player experience. The architecture must still be adjusted for local data classification, recovery objectives, workload shape and application behaviour.

The lesson we would carry into the next project

Modernisation stopped meaning 'replace everything'. It became a controlled transfer from personal knowledge to a shared, testable platform practice.

The strongest open-source platforms are not the ones with the most automation. They are the ones where automation makes ownership, risk and recovery easier for people to understand.