Microsoft Azure
- reference
Couchbase Capella supports deploying databases onto Microsoft Azure.
Couchbase Capella provides fully managed Couchbase Server databases that you can deploy onto Microsoft Azure. This page describes the various regions and configurations available to you when using Capella with Azure.
Supported Regions
Couchbase Capella’s fully managed DBaaS supports the following Azure regions.
-
Americas
-
Europe
-
Asia Pacific
Azure Region | Location | Ultra Disk Support | Trial Support [1] |
---|---|---|---|
|
East US (Virginia) |
✔ |
✔ |
|
East US 2 (Virginia) |
✔ |
|
|
Canada Central (Toronto) |
✔ |
|
|
West US 2 (Washington) |
✔ |
|
|
West US 3 (Arizona) |
✔ |
|
|
South Central US (Texas) |
✔ |
|
|
Brazil South (São Paulo) |
Azure Region | Location | Ultra Disk Support | Trial Support [1] |
---|---|---|---|
|
Norway East (Oslo) |
||
|
UK South (London) |
✔ |
|
|
West Europe (Netherlands) |
✔ |
|
|
Sweden Central (Gävle) |
✔ |
✔ |
|
Switzerland North (Zürich) |
Azure Region | Location | Ultra Disk Support | Trial Support [1] |
---|---|---|---|
|
Australia East (New South Wales) |
✔ |
|
|
Korea Central (Seoul) |
✔ |
|
|
Central India (Pune) |
||
|
East Asia (Hong Kong) |
[1] A self-service trial can deploy a database to this Azure region.
Availability Zones
All the Microsoft Azure regions that Capella supports have availability zones. Availability zones are data centers that Azure groups together within a region. They are maintained in separate physical locations within a region and isolated from failures in other zones.
Capella can automatically distribute database nodes across multiple availability zones in a region for the highest availability. For example, a three-node database could deploy one node to each of the three availability zones in a region. A failure in one of these availability zones wouldn’t impact the other two nodes that could remain in operation.
Except for self-service trials, databases in Capella deploy with a minimum of three nodes. Databases deployed with Azure use Couchbase Server 7.1 or later, which supports unequal server groups.
The Multiple Zones option is the default when creating databases using the Developer Pro or Enterprise Service Plans.
The option to deploy across multiple Azure availability zones is only available for databases that use the Developer Pro or Enterprise Service Plans. Databases using the Basic service plan deploy all nodes to the same availability zone. |
Configuration Options
Customize the databases you deploy with Microsoft Azure to fit your requirements using the following configuration options:
Nodes
As they’re intended for evaluation purposes only, self-service trial databases only include one node. |
Databases have a minimum of 3 nodes and a maximum of 27.
Databases consist of service groups that include the services deployed and system resources. Each service group has a node quantity representing the number of nodes in the database with that configuration. Individual service groups can have between 2 and 27 nodes but cannot collectively exceed 27. The service group that includes the Data Service requires at least three nodes.
Compute and Memory
The following compute configuration options are available for databases on Microsoft Azure.
vCPU | Memory | Azure VM |
---|---|---|
2 vCPUs [2] |
8 GiB |
Standard_D2s_v5 |
4 vCPUs |
16 GiB |
Standard_D4s_v5 |
4 vCPUs |
32 GiB |
Standard_E4s_v5 |
8 vCPUs |
16 GiB |
Standard_F8s_v2 |
8 vCPUs |
32 GiB |
Standard_D8s_v5 |
8 vCPUs |
64 GiB |
Standard_E8s_v5 |
16 vCPUs |
32 GiB |
Standard_F16s_v2 |
16 vCPUs |
64 GiB |
Standard_D16s_v5 |
16 vCPUs |
128 GiB |
Standard_E16s_v5 |
20 vCPUs |
160 GiB |
Standard_E20s_v5 |
32 vCPUs |
64 GiB |
Standard_F32s_v2 |
32 vCPUs |
128 GiB |
Standard_D32s_v5 |
32 vCPUs |
256 GiB |
Standard_E32s_v5 |
48 vCPUs |
96 GiB |
Standard_F48s_v2 |
48 vCPUs |
192 GiB |
Standard_D48s_v5 |
48 vCPUs |
384 GiB |
Standard_E48s_v5 |
64 vCPUs |
128 GiB |
Standard_F64s_v2 |
64 vCPUs |
256 GiB |
Standard_D64s_v5 |
64 vCPUs |
512 GiB |
Standard_E64s_v5 |
72 vCPUs |
144 GiB |
Standard_F72s_v2 |
96 vCPUs |
384 GiB |
Standard_D96s_v5 |
96 vCPUs |
672 GiB |
Standard_E96s_v5 |
[2] This configuration is only available for self-service trial databases in Capella.
Storage
The Capella databases you deploy onto Azure can use Premium SSDs (v1) or Ultra disks.
When using Azure’s Premium SSDs (v1), the amount of storage available per node in your database depends on the chosen disk type. For example, if you want the 256 GiB of storage, you could choose the P15 disk configuration. If you’re using the Ultra disk type, you can choose between fixed storage size options.
IOPS (input/output operations per second) measures the storage speed of a database. Premium storage disk speed is based on the chosen disk type and can’t be separately set. Ultra disk speed can be set, but the possible range depends on the chosen disk size.
-
For more information on Premium SSDs and disk types that Capella offers, see Premium SSD Type.
-
For more information on Ultra disks and the configuration options that Capella offers, see Ultra Disks.
Premium SSD
Azure premium SSDs are best for high-performance database needs that require lower latency and more IOPS. The following Azure premium SSD sizes are available in Capella:
Type | Disk size (GiB) | Provisioned IOPS per disk [3] |
---|---|---|
P6 |
64 |
240 |
P10 |
128 |
500 |
P15 |
256 |
1,100 |
P20 |
512 |
2,300 |
P30 |
1,024 |
5,000 |
P40 |
2,048 |
7,500 |
P50 |
4,096 |
7,500 |
P60 |
8,192 |
16,000 |
[3] The guaranteed number of IOPS per the disk specification. See Premium SSD size for more information.
Ultra Disk
Azure Ultra Disks are best for intensive and transaction-heavy workloads. They offer the lowest latency and consistent IOPS/throughput while providing scalability. Ultra Disks are available to databases hosted in Azure regions that support it. To see what regions support this option, see the regions list.
The Ultra Disk option allows you to choose a storage size and IOPS. By default, this is 64 Gib, but you choose from the following:
Disk size (GiB) | IOPS Cap |
---|---|
64 |
19,200 |
128 |
38,400 |
256 |
76,800 |
512 |
80,000 |
1,024 — 15,360 (In increments of 1 TiB) |
80,000 |
Adjusting the IOPS rate affects performance and cost. When creating or modifying a database with the Azure Ultra Disk storage option, Capella uses recommended defaults for the IOPS field. You can replace a default IOPS value with one higher than the default but not lower. For the recommended IOPS values for databases using Azure Ultra Disks with typical enterprise workloads, see IOPS Defaults. |
Integrations with Azure
Couchbase Capella has further integrations with Azure, allowing you and your applications to use Capella more effectively with existing assets:
-
Azure Virtual Network: Configure a Private Network with Azure.
-
Azure Private Link: Add an Azure Private Link Connection
-
Azure Active Directory (AD): Configure SSO authentication to the Capella UI with Azure AD.