Skip to Content
We annotated Google’s Zanzibar paper with extra context and SpiceDB comparisons. [Read the annotated paper]
Managed SpiceDBConceptsWorkload Isolation and QoS

Workload Isolation and QoS

Available onCloudDedicatedOpen Source (build it yourself)Enterprise (build it yourself)

Other workloads running on the same machines as SpiceDB can slow down your permission checks, especially at the tail of your latency distribution (p99). This is often called the “noisy neighbor” problem.

AuthZed protects your SpiceDB deployments from noisy neighbors at two levels:

LevelCloudDedicated
Workload QoS
Full Workload IsolationNot included

Workload QoS

Every SpiceDB pod gets a fixed amount of CPU and memory that is reserved for it. Other workloads can’t use that share, and your pods are the last to be evicted if a node runs low on memory.

SpiceDB also runs on nodes that are separate from AuthZed’s own platform services (see Control Plane), so management and monitoring work never competes with your permission checks.

On AuthZed Cloud, SpiceDB nodes are shared with other Cloud customers’ deployments. Your CPU and memory are reserved, but other resources on a node, such as CPU caches, memory bandwidth and network bandwidth, are shared.

Full Workload Isolation

AuthZed Dedicated runs in a cloud account and Kubernetes cluster dedicated to your organization, so no other customer’s workloads run on your machines.

Within that cluster, permission systems marked as production run on node pools used only by that permission system. Development permission systems share a node pool with your other development permission systems.

Full Workload Isolation includes Workload QoS: SpiceDB pods on Dedicated also get reserved CPU and memory.

Control Plane

Services that are secondary to serving real-time requests run as one shared workload called the control plane, on nodes separate from SpiceDB.

These services include:

  • AuthZed management UI and its accompanying machinery
  • Observability services for the SRE team (e.g. Prometheus, Grafana, Jaeger)
  • Compliance infrastructure

Example Architecture Diagram

This example shows an AuthZed Dedicated cluster, with SpiceDB pods and control plane services running on separate nodes.

Workload Isolation Diagram

Low-latency Workloads on Kubernetes

AuthZed has presented a video to the CNCF  documenting some of the critical components to running low-latency workloads on Kubernetes. The technologies presented partially describe the implementation of Workload Isolation in AuthZed products: