Join our Newsletter — 33% off our NHI Course

Why did Databroker move off Postgres for session state?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Databroker moved to local file storage with Raft clustering because Postgres can become hard to operate for session state, directory sync, and replicated authorization data at scale, according to Pomerium. Access state now has to be recoverable and replicable fast enough to match the decisions identity systems make.

Editorial analysis by NHI Mgmt Group, based on content published by Pomerium: “Sometimes Postgres isn’t the Answer”.

Key questions

Q: When does Postgres become the wrong choice for access-proxy state?

A: Postgres becomes a poor fit when the real problem is not data storage alone but low-latency replication, simple recoverability, and easy day-two operations at scale.

Q: How can teams tell whether authorization state is actually recoverable?

A: A useful test is whether sessions and directory context can be rebuilt quickly after a restart without manual repair.

Q: What breaks when identity is treated as a login layer only?

A: When identity is treated as a login layer only, teams miss the fact that many high-risk decisions happen after authentication, inside delegated workflows and tool chains.

Practitioner guidance

  • Audit identity-state dependencies Map which authorization decisions depend on session data, directory sync, and external context that must remain current between logins.
  • Separate recomputable context from authoritative state Classify which access inputs can be rebuilt after restart and which ones must remain continuously durable for policy enforcement.
  • Measure state replication latency Test how quickly a membership change, session update, or policy-relevant record reaches every proxy or databroker instance.

Bottom line: Identity-aware access proxies can lose policy fidelity when session and directory state are tied to storage patterns that do not match real operational load.

Glossary terms: Databroker, Directory Sync, Recovery-Oriented Storage, Raft Leader Election

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Identity enforcement fails when policy state is treated like ordinary application data. This article shows that access decisions depend on state freshness, recoverability, and operational accessibility, not simply on choosing a familiar database. When directory data changes faster than the storage pattern can absorb, authorization drifts away from the identity source of truth. Practitioners should treat state design as part of the access-control model, not just platform plumbing.

A question worth separating out:

Q: Should IAM teams centralize all policy data in one datastore?

A: Not always. Centralization only helps when the datastore can sustain the read-write pattern, replication needs, and operational support model of the access system. For some identity workloads, simpler local persistence with controlled clustering is easier to govern than a shared database that becomes the bottleneck.

👉 Read our full editorial: Databroker’s storage shift shows when Postgres stops fitting


This post was modified 7 days ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.