# Temporal recommendation for Cassandra setup at production level

**URL:** <https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898>\
**Category:** Community Support\
**Tags:** cassandra, deployment\
**Created:** [June 6, 2022, 5:24pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898 "2022-06-06T17:24:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![poojabhutada](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/poojabhutada/32/3372_2.png) [@poojabhutada](https://community.temporal.io/u/poojabhutada)\
**Post date:** [June 6, 2022, 5:24pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898/1 "2022-06-06T17:24:45Z")

</div>

Hi,

I have a couple of queries regarding Temporal deployment with Cassandra. We are planning to have a separate Cassandra setup and point the same for Temporal persistence. Looking for answers on the same.

1. What is the default consistency that temporal provides with Cassandra deployment(helm chart)? What is temporal recommendation of consistency level with Cassandra for production level setup?
2. Also, I could see 2 attributes in temporal helm chart deployment with cassandra i.e consistency and serialConsistency. Can you explain the significance of both?
3. What is the replication factor of Cassandra suggested for a production level setup?

Regards,  
Pooja Bhutada

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [June 6, 2022, 9:40pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898/2 "2022-06-06T21:40:07Z")

</div>

1, 2. You mean read/write consistency? Temporal by default uses LOCAL\_QUORUM (consistency param, same as gocql Consistency values) / LOCAL\_SERIAL (serialConsistency param, same as gocql SerialConsistency values). This should be fine unless you have a need to change it.  
3. For prod the typical recommendation is to use replication factor of 3 for the core temporal keyspace. You can start with 5 Cassandra hosts each having 16 cores and 32 gb mem

---

<div class="post-metadata">

**Author:** ![poojabhutada](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/poojabhutada/32/3372_2.png) [@poojabhutada](https://community.temporal.io/u/poojabhutada)\
**Post date:** [June 7, 2022, 3:37pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898/3 "2022-06-07T15:37:24Z")

</div>

Thanks @tihomir . One followup question regarding number of Cassandra setup that you suggested. Do you mean 5 separate Cassandra hosts and each having replication factor of 3??

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [June 7, 2022, 4:32pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898/4 "2022-06-07T16:32:14Z")

</div>

It should mean to have 5 Cassandra nodes in your cluster and set replication factor to 3.  
All the replicas should be spread across the 5 Cassandra instances.

---

<div class="post-metadata">

**Author:** ![poojabhutada](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/poojabhutada/32/3372_2.png) [@poojabhutada](https://community.temporal.io/u/poojabhutada)\
**Post date:** [June 7, 2022, 5:22pm UTC](https://community.temporal.io/t/temporal-recommendation-for-cassandra-setup-at-production-level/4898/5 "2022-06-07T17:22:05Z")

</div>

Got it…Thank you!
