paper:zanzibar#translation@you
Zanzibar: Google’s Consistent, Global Authorization System
Pang et al., 2019 USENIX Annual Technical Conference (USENIX ATC ’19). Read paragraph by paragraph, the original English next to one of eight translations.
- 日本語Zanzibar: Google の一貫性を備えたグローバル認可システムmatches your browser
- 简体中文Zanzibar:Google 的一致性全球授权系统matches your browser
- 繁體中文Zanzibar:Google 的一致性全球授權系統matches your browser
- 한국어Zanzibar: Google의 일관된 글로벌 인가 시스템matches your browser
- EspañolZanzibar: el sistema de autorización global y consistente de Googlematches your browser
- FrançaisZanzibar : le système d’autorisation global et cohérent de Googlematches your browser
- DeutschZanzibar: Googles konsistentes, globales Autorisierungssystemmatches your browser
- Português (Brasil)Zanzibar: o sistema de autorização global e consistente do Googlematches your browser
- EnglishThe original alone, without a translationmatches your browser
Guides
Background for reading the paper: the access-control models it builds on, the history behind it, and its mechanisms drawn step by step.
- ACL, RBAC, ABAC, ReBAC: four ways to say who may do what
- From Multics to Zanzibar
- Relation tuples and usersets
- Consistency, snapshots and zookies
- Architecture, from one Check to Spanner
- Inside one Check
- Leopard, the group index
- Listing what a user can see
- Keeping tuples in step with your data
- Modeling patterns: from rewrite rules to real permissions
- When relationships are not enough
- Ordering without TrueTime
- Changing and testing a schema
- Do you need a Zanzibar?
- Common misconceptions
- Glossary
Ecosystem
Systems built on the paper's ideas: how each maps Zanzibar's concepts, with its schema, architecture and differences.
The original paper at USENIXSource and issues on GitHub
Unofficial translation. Not affiliated with or endorsed by Google, USENIX or the authors. The paper is © 2019 its authors and was published at USENIX ATC ’19. Translated with AI assistance and checked against the original. Errors may remain.