Permission Systems for Enterprise That Scale
eliocapella.com
Permission Systems for Enterprise That Scale
1–10 of 39 posts
Re: Permission Systems for Enterprise That Scale
#2If you're using Postgres then using the ltree module is great for permission systems. Available in RDS too
Re: Permission Systems for Enterprise That Scale
#3[deleted]
Re: Permission Systems for Enterprise That Scale
#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 class support for it.
Re: Permission Systems for Enterprise That Scale
#5Strange 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)
Re: Permission Systems for Enterprise That Scale
#6If you're using Postgres then using the ltree module is great for permission systems. Available in RDS too
Could you explain why this is great over alternatives?
Re: Permission Systems for Enterprise That Scale
#7Strange 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)
Re: Permission Systems for Enterprise That Scale
#8If you're using Postgres then using the ltree module is great for permission systems. Available in RDS too
Do you have an article about that?
Re: Permission Systems for Enterprise That Scale
#9>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?
Re: Permission Systems for Enterprise That Scale
#10>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?
I don't think you are missing anything. I think he is just pointing out that technically nothing is enforcing this synchronization, so if someone forgets to wrap things in a transaction, it could get out of sync.