RDR-002 Accepted Core Infrastructure

Standardize on PostgreSQL for Auditable Metadata & Ledger Persistence

Adopt PostgreSQL 17+ as the canonical relational store for provenance graphs, evaluation records, and cryptographic audit logs.

Recorded: 2026-08-28
Review Cycle: Annual (Next: 2027-08)

Context & Problem Statement

ResourceRank registries require a storage engine capable of enforcing strict relational constraints across assessments, evidence artifacts, and historical revisions while remaining free of single-vendor licensing hazards.

Evaluated Options

  1. PostgreSQL 17 (Score: 96/100): Permissive BSD-style license, mature JSONB indexing, strong ACID guarantees, and broad managed/self-hosted parity.
  2. Proprietary Cloud NewSQL Services: High operational convenience but introduces vendor lock-in and opaque engine internals.

Decision

We adopt PostgreSQL 17+ as the baseline persistence engine for all ResourceRank reference deployments. All schema migrations must remain compliant with standard SQL and avoid proprietary hosted extensions.

Consequences

  • Positive: Zero licensing friction; deterministic point-in-time recovery; native jsonb support for flexible evidence payloads.
  • Trade-off: Horizontal write sharding requires explicit application-level partitioning beyond single-node capacity.