Why should you care?

A bank on PostgresVerse separates core banking, loans, and audit schemas so teams deploy independently while sharing customer master data safely.

See it live — copy this example

Run in pgAdmin or psql.

-- Domain split in PostgresVerse
CREATE SCHEMA core;
CREATE SCHEMA audit;
CREATE TABLE core.accounts (
  account_id bigserial PRIMARY KEY,
  customer_id bigint NOT NULL,
  balance numeric(14,2) NOT NULL DEFAULT 0
);
CREATE TABLE audit.account_changes (
  change_id bigserial PRIMARY KEY,
  account_id bigint NOT NULL,
  changed_at timestamptz DEFAULT now(),
  old_balance numeric(14,2),
  new_balance numeric(14,2)
);

What happened?

• core holds live balances; audit append-only history supports compliance.
• Splitting schemas lets you grant auditors read on audit only.
• Numeric(14,2) suits ledger precision.

Practice next

1. Create core and audit schemas in PostgresVerse.
2. Create both tables and insert sample account plus audit row.
3. Document which team owns each schema in a README.
4. Add a read-only role audit_reader GRANT SELECT ON audit.account_changes.
5. Sketch a third schema reporting for materialized views.

Remember

Schema boundaries mirror team boundaries. Audit tables are often append-only. Document FK direction and retention policies early.

PostgresVerse bank blueprint

Architects split OLTP core from audit before RBI review.

Outcome: Pen testers get scoped credentials that cannot touch live balances.