Google stands on it.
Zanzibar: Google’s Consistent, Global Authorization System (2019)
11–20 of 99 posts
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#12It’s so tempting to make some snide remark about it being cancelled.
I hope not, I just finished integrating with it at work.
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#13I'm curious what's driving the resurgence in interest authorization infrastructure, particularly the Zanzibar paper. As founder of Oso ( https://www.osohq.com/ ), I have my own opinions, and I think this is a good thing. But would love to hear others' points of view here.
Some factors might include increasing usage of microservices, frontend SPAs, serverless, and more early startups looking to integrate with enterprises, who now have high expectations of what's possible thanks to Auth0 and the like.
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#14I'm curious what's driving the resurgence in interest authorization infrastructure, particularly the Zanzibar paper. As founder of Oso ( https://www.osohq.com/ ), I have my own opinions, and I think this is a good thing. But would love to hear others' points of view here.
My guess is that it is mainly driven by the increasing adoption of microservice (or just generally more distributed architectures). Doing fine-grained authorization in that type of architecture quite difficult and people are starting to realize that.
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#15Maybe a dumb question on standalone authorization services: does the authorization service end up having a representation for every single object in all of the rest of your datastores? (e.g. every document, every blob of storage, every user in every org).
If so, does that become a chokepoint in a distributed microservice architecture? Or can that be avoided with an in-process or sidecar architecture in which a given microservice's objects are not separately referenced in auth persistence? If not, how do folks determine which objects to register with the auth service and which to handle independently?
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#16Google stands on it.
I also immediately think of the Brunner book
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#17[deleted]
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#18Reminds me how how Basecamp would have acted during WW2 as well. Nothing to do with business so take it outside.
Re: Zanzibar: Google’s Consistent, Global Authorization System (2019)
#19Reminds me how how Basecamp would have acted during WW2 as well. Nothing to do with business so take it outside.
Did you reply to the wrong thread?