Data plane infrastructure components
This topic lists the infrastructure components deployed in the Data Plane and their roles.
These components are deployed in your Azure Subscription as part of the overall deployment process. All components that are deployed are configured and managed by Db2® SaaS and should not be modified or changed.
| Component | Description |
|---|---|
| ServiceBus | Provides communication between IBM Control Plane and your Data Plane. A Basic Tier ServiceBus is provisioned in the your subscription. |
| Azure Storage Account | Provides storage for the Db2 SaaS including Azure Blob and Premium SSD v2 block storage. We create three storage accounts for infrastructure components and an additional storage account per engine instance deployed. Premium disk storage is allocated based on the block storage used by the Engine instances. |
| Logic Apps | A serverless platform for automating long running service management workflows (consumption). |
| Azure Functions | A serverless compute that runs workflows in response to events for management (Flex consumption). |
| Azure Monitor | Provides monitoring and logging capabilities for service workflows. |
| Azure Redis cache | For persistent database monitoring metadata. A basic instance of capacity 1 GB is provisioned initially. |
| Azure Lighthouse | Provides limited access privileges to data processing infrastructure. It allows IBM SRE to securely manage and debug issues on Db2 SaaS BYOC running in the Data Plane. |
| Azure API Management | Provides REST interfaces for management capabilities (consumption). |
| Azure Virtual Machines | For service orchestration and instance management. |
| AKS | Azure Kubernetes Service to host data processing compute. An AKS cluster spanning three zones is created as part of the Data Plane setup process. |
| Azure Load Balancers | Used for network connectivity. These load balancers are created when an Engine instance is deployed. |
As part of actual Db2 SaaS Engine instance provisioning, different VM types can be selected and will be provisioned to host your database engine. You can decide on the size of VM to use based on your expected workload, although this can be updated at a later time as well from the Db2 SaaS Console.