Google Zanzibar

Zanzibar functions as an authorization service. It processes access control queries from client applications and stores access control lists (ACLs) expressed as relationship tuples under a relationship-based access control (ReBAC) model. Each tuple represents a subject, a relation, and an object. The system is designed to provide consistency, fault tolerance, and scalability for applications with large user bases. == Architecture ==

Zanzibar's architecture includes several core components: == Performance ==

The system uses techniques such as cache prefetching and selective invalidation of frequently accessed permissions to reduce latency. == Relationship to ReBAC ==

Zanzibar employs relationship-based access control (ReBAC), in which authorization decisions depend on relationships between entities rather than predefined roles. In contrast, role-based access control (RBAC) assigns permissions based on user roles. Zanzibar's use of ReBAC enables dynamic access control in collaborative environments such as document-sharing systems. == Industry influence ==

The Zanzibar research paper has influenced the design of other authorization systems based on ReBAC principles. Examples include Airbnb's internal system Himeji and several open-source projects that adopt similar models. == Limitations ==

Implementing a Zanzibar-like system requires substantial engineering and infrastructure resources. Maintaining replication, caching, and schema configurations adds operational complexity. The tuple-based relationship model may fail to capture certain policy logic, requiring integration with additional rule-based or policy engines. == See also ==