Scylla Cloud Best Practices

  • While Creating your cluster, make sure you enable VPC peering.

    VPC peering is more secure, it will save network costs and it has no downsides.

    Enabling this will also allow you future flexibility by using features that require this setting. Read more here.

  • Always choose NetworkTopology as Replication Strategy for all your Keyspaces. Using SimpleStrategy will not provide High Availability in case of an Availability Zone (AZ) failure, and will not allow multiple Data Centers(DC) setup.

    Read more in Scylla Docs or Scylla University

  • Use Consistency Level of Quorum for one DC, or Local Quorum for Multi DC cluster.

  • Use Replication Factor(RF) of at least 3 per Data Center. A lower number of replicas will provide neither HA nor strong consistency.

  • When sizing your cluster, make sure you have at least 50% free disk space for cluster backup and other maintenance routines (e.g: compaction)

  • When Scylla Cloud is deployed in your AWS account, make sure you set all your AWS account limits with the needed additional allocations for Scylla Cloud. See Deploy Scylla Cloud on your AWS Account user guide for the needed resources and limits.

  • During your cluster lifetime, its server’s IP address might change. Make sure your application connection string is always up-to-date with the cluster IPs. Use the Scylla Cloud UI ‘VIEW CLUSTER’ page to see the relevant PUBLIC IP addresses.