---
name: netezza-architecture-workload-isolation
title: Learning about NPSaaS architecture and workload isolation
description: For AWS, the model uses EKS (an AWS-managed Kubernetes platform) for each customer and each instance.
last-updated: 2024-06-14
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/netezza?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

{:external: target="_blank" .external}
{:shortdesc: .shortdesc}
{:table: .aria-labeledby="caption"}
{:tip: .tip}
{:important: .important}
{:note: .note}
{:caption: .caption}

# Learning about NPSaaS architecture and workload isolation
{: #compute-isolation}

IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service uses a multi-tenant-in-a-cluster isolation model.

For Azure, the model uses a separate OpenShift namespace for each customer and each instance.
For AWS, the model uses EKS (an AWS-managed Kubernetes platform) for each customer and each instance.
{: shortdesc}

## NPSaaS architecture
{: #architecture}

![NPSaaS architecture](../images/Netezza-Deployment-diagram.png){: caption="Image 1. The diagram depicts the deployment model and how the workload isolation is ensured." caption-side="bottom"}


## NPSaaS workload isolation
{: #workload-isolation}

Customer data and compute storage are isolated from other instances.  Each provisioned instance has a seperate set of worker nodes and separate Cloud Object Storage buckets for customer data. DR Backups are also stored in a customer-specific encrypted Cloud Object Storage bucket.