Note : Free trial customers are restricted to a specific number of developer nodes and are not able to create all the prerequisite clusters needed for Advanced Visibility.
Step 1 – Configure your supporting clusters
To provision your Advanced Visibility Cadence cluster, you will first need to use Instaclustr’s managed service to provision the prerequisite clusters (i.e. Apache Cassandra®, OpenSearch, Apache Kafka®). This can be done via the Instaclustr Console.
Take care to provision a version 3.11.x Cassandra cluster here, rather than a version 4.x cluster (both versions are provisionable in the console). There are compatibility issues between Cassandra 4 and Cadence that we expected to see rectified in an upcoming Cadence release.
Note: The cluster creation wizard for all three clusters above will offer you the option to designate the cluster as a ‘Bundled Use Only’ cluster, which can enable discounted pricing for these clusters in certain use cases. We recommend reading more about Bundled Use Only Cluster Deployments to assess if this could be an advantageous feature for your use case.
Step 2: Create a Cadence cluster
Now that we have prepared our required clusters, we can create a Cadence cluster and configure it to use them.
Log into theInstaclustr Console and click the CreateCluster button. When prompted, select the Cadence application.
On the Cadence Setup page, we can select the version of Cadence. We are currently only offering Cadence 0.22.4. Make sure to enable the Use Advanced Visibility option and continue.
On the Cadence Dependency Setup page, you will be given the option to specify your supporting clusters for the Cadence cluster, and to configure the connections between the clusters. In each section, select the Cassandra, OpenSearch or Kafka cluster that you wish to use as the supporting cluster. Additionally, you can specify the VPC configuration that you would like to exist between your Cadence cluster and each of the supporting clusters in the ‘VPC Configuration’ dropdown.
The options are:
Separate VPC (default) – The Cadence cluster will be created in a separate virtual network to the supporting cluster and they will communicate over public IP addresses.
VPC Peering – The Cadence cluster will be created in a separate virtual network to the supporting cluster, but those two networks will be peered together, allowing communication over private IP addresses.
This configuration is most applicable if your Cassandra cluster is set to Private RPC Broadcast or Private Network Cluster where client-server communication is over private IP addresses.
This configuration is only available on AWS right now; this functionality will be supported for other providers in the near future.
Cassandra VPC – Instaclustr will provision the Cadence cluster into the same virtual network as that specific supporting cluster.
This configuration can be useful if you need to minimise cross-VPC data transfer costs.
On the Data Centre page:
Select a Data Centre Region,
A Cluster Network address block,
The number of nodes for your application,
Your desired node size.
The Confirmation page displays a brief summary of your cluster configurations and pricing details. If you are happy with the cluster configuration and have accepted the terms and conditions, click the Create Cluster button to start provisioning the cluster.
Instaclustr’s provisioning system will begin to create the Cadence cluster instances. In the Cluster Details page we can monitor the progress of the provisioning steps. Once the cluster reaches a Running state, you have finished creating your Advanced Visibility Cadence cluster!