Polyglot freshness (Postgres ↔ Neo4j sync)

Generated from mcp/patterns.registry.json — do not edit by hand; change the registry and run bun run patterns:build.

Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.

Category: Databases & Storage · Tier: light · Risk: medium — spans two external managed services (Postgres, Neo4j)

Documents strategies for keeping references between Postgres and Neo4j valid, since no foreign keys exist across the two stores.

When to use: Apply when a delete or update in one store, such as a Postgres user or item, must propagate to or invalidate related Neo4j nodes.

Docs

• docs/blueprint/db/polyglot-freshness.md (GitHub · GitLab)

Code

• src/lib/server/graph/catalog.ts (GitHub · GitLab)

Machine-readable record: databases-polyglot-freshness in mcp/patterns.registry.json.