Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions app/authzed/concepts/deployments/page.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,8 @@ There is no global endpoint that automatically routes requests to the nearest De

## Workload isolation

Deployments on AuthZed Dedicated and Cloud run on hardware dedicated to your organization, separate from the shared control plane services (such as the Management Dashboard and observability tooling).
See [Workload Isolation] for details.
Deployments on AuthZed Cloud and Dedicated run on nodes separate from the shared control plane services (such as the Management Dashboard and observability tooling), with CPU and memory reserved for each SpiceDB pod.
On AuthZed Dedicated, the cloud account and cluster are also dedicated to your organization; on AuthZed Cloud, SpiceDB nodes are shared with other Cloud customers.
See [Workload Isolation and QoS] for details.

[Workload Isolation]: workload-isolation
[Workload Isolation and QoS]: workload-isolation
45 changes: 38 additions & 7 deletions app/authzed/concepts/workload-isolation/page.mdx
Original file line number Diff line number Diff line change
@@ -1,28 +1,59 @@
---
title: "Workload Isolation"
description: "AuthZed functionality that gives SpiceDB deployments dedicated hardware to guarantee performance and prevent noisy neighbor problems."
title: "Workload Isolation and QoS"
description: "How AuthZed Cloud and Dedicated protect SpiceDB deployments from noisy neighbors, with reserved resources on Cloud and fully isolated infrastructure on Dedicated."
---

import YouTube from "@/components/youtube-wrapper";

# Workload Isolation
# Workload Isolation and QoS

Workload Isolation gives your SpiceDB deployments access to hardware that is only used by you, to guarantee performance and prevent "noisy neighbor" problems.
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:

| Level | [Cloud] | [Dedicated] |
| --------------------------------------------------- | :--------: | :---------: |
| [Workload QoS](#workload-qos) | <Yes /> | <Yes /> |
| [Full Workload Isolation](#full-workload-isolation) | <Absent /> | <Yes /> |

[Cloud]: ../guides/picking-a-product#cloud
[Dedicated]: ../guides/picking-a-product#dedicated

## 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](#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.
Each SpiceDB pod is pinned to its own whole CPU cores, which no other workload on the node can run on, and its memory is reserved.
Other resources on a node, such as CPU caches, memory bandwidth and network bandwidth, are still 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 one shared workload called the 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

## Workloads

## Example Architecture Diagram

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

![Workload Isolation Diagram](/images/workload-isolation-diagram.png)

## Low-latency Workloads on Kubernetes
Expand Down
6 changes: 4 additions & 2 deletions app/authzed/guides/picking-a-product/page.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,8 @@ This document is designed to give a high-level overview of the features supporte
| ↳ [Event Streams (Early Access)] | <Absent /> | <Absent /> | <Yes /> | <Absent /> |
| [Management Dashboard] | <Absent /> | <Yes /> | <Yes /> | <Absent /> |
| [Private Networking] | DIY | <Absent /> | <Yes /> | DIY |
| [Workload Isolation] | DIY | <Yes /> | <Yes /> | DIY |
| [Workload QoS] | DIY | <Yes /> | <Yes /> | DIY |
| [Full Workload Isolation] | DIY | <Absent /> | <Yes /> | DIY |
| [Automated Updates] | DIY | <Yes /> | <Yes /> | DIY |
| [SOC2 Compliance] | DIY | <Yes /> | <Yes /> | DIY |
| [Audit Logging] | <Absent /> | <Yes /> | <Yes /> | <Yes /> |
Expand All @@ -51,7 +52,8 @@ This document is designed to give a high-level overview of the features supporte
[Security Embargo]: ../concepts/security-embargo
[Expedited Support]: https://authzed.com/pricing#support-packages
[Private Networking]: ../concepts/private-networking
[Workload Isolation]: ../concepts/workload-isolation
[Workload QoS]: ../concepts/workload-isolation#workload-qos
[Full Workload Isolation]: ../concepts/workload-isolation#full-workload-isolation
[Restricted API Access]: ../concepts/restricted-api-access
[Rate Limiting]: ../concepts/rate-limiting

Expand Down
Loading