>But authz is far more complicated, since it requires an ACL list of arbitrary length along with the token. It’s not like GitHub can stuff a list of every repository I can access into my access token.
This is exactly the problem that Zanzibar solves that makes it exciting!
I've written about why giant lists of claims are not a good way to structure permission systems[0] and Zanzibar-inspired services do not function this way.
Instead they ask you to query the API server when you need to check access to an item.
All API calls return a response along with a revision.
The response will always the same at a given revision, which means you can cache the response.
If Zanzibar disappears, your app can function so long as content is not modified, which would force you to invalidate the revision.
And that's only if you want consistency in your permission system -- a feature that not all permission systems even support.
Most applications can tolerate just using the cached response regardless and relying on eventual consistency.
All of this is also ignoring the global availability of the Zanzibar service itself which it gets from using a distributed database like Spanner and replicating into data centers in every region in the world (which is why you want someone else to run it for you).
This is exactly the problem that Zanzibar solves that makes it exciting! I've written about why giant lists of claims are not a good way to structure permission systems[0] and Zanzibar-inspired services do not function this way. Instead they ask you to query the API server when you need to check access to an item. All API calls return a response along with a revision. The response will always the same at a given revision, which means you can cache the response. If Zanzibar disappears, your app can function so long as content is not modified, which would force you to invalidate the revision. And that's only if you want consistency in your permission system -- a feature that not all permission systems even support. Most applications can tolerate just using the cached response regardless and relying on eventual consistency.
All of this is also ignoring the global availability of the Zanzibar service itself which it gets from using a distributed database like Spanner and replicating into data centers in every region in the world (which is why you want someone else to run it for you).
[0]: https://authzed.com/blog/identity-isnt-the-foundation/