Permission Systems for Enterprise That Scale

Post by eliocs » Wed, Dec 24, 2025, 2:18 PM UTC

valiant55 wrote: post #9

charcircuit wrote: post #4

>We added a point of failure, as the permissions table can get out of sync with the actual data. >The main risk with pre-computed permissions is data getting out of sync. It would make sense to have permissions be a first class concept for databases and to ensure such a desync could never happen. Data being only read or written from specific users is a very common thing for data so it would be worth having first clas…

I'm struggling to understand what the issue that the author is getting at. The point of a database is that it's ACID compliant, wrap insets/updates/deletes in a transaction and no such drift would occur. What am I missing?

Post by eliocs » Wed, Dec 24, 2025, 2:23 PM UTC

Xmd5a wrote: post #11

https://docs.feldera.com/use_cases/fine_grained_authorizatio... Fine-grained authorization as an incremental computation problem

Post by phrotoma » Wed, Dec 24, 2025, 3:16 PM UTC

eliocs wrote: post #13

tekkk wrote: post #5

Strange the article proposes itself for "Enterprise" yet has no mention of Google's Zanzibar and how it compares to the other approaches. AFAIK it doesn't use pre-computed values but just queries really fast (using Spanner so there's that)

Can you let me know how would you for example query all accessible resources for a user using Google's Zanzibar?

Post by gneray » Wed, Dec 24, 2025, 3:34 PM UTC

Xmd5a wrote: post #11

https://docs.feldera.com/use_cases/fine_grained_authorizatio... Fine-grained authorization as an incremental computation problem

Post by svaha1728 » Wed, Dec 24, 2025, 5:24 PM UTC

tekkk wrote: post #5

Strange the article proposes itself for "Enterprise" yet has no mention of Google's Zanzibar and how it compares to the other approaches. AFAIK it doesn't use pre-computed values but just queries really fast (using Spanner so there's that)