# Support for Vitess / Amazon Keyspaces

**URL:** <https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910>\
**Category:** Community Support\
**Created:** [April 12, 2021, 10:50pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910 "2021-04-12T22:50:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arjunraman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/arjunraman/32/865_2.png) [@arjunraman](https://community.temporal.io/u/arjunraman)\
**Post date:** [April 12, 2021, 10:50pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/1 "2021-04-12T22:50:33Z")

</div>

Hello,

We are building a new workflow system on top of temporal and anticipate having millions of running executions (mostly waiting for signal), with thousands of actively running workflow executions.

We aren’t sure if a single shard MySQL db can cope with this scale, and wanted to know if you support Vitess? We have a team managing Vitess in our company and that would be ideal for us. If Vitess isn’t supported, do you supporting AWS managed Cassandra offering (AWS Keyspaces)?

Thanks,  
Arjun

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [April 12, 2021, 11:10pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/2 "2021-04-12T23:10:38Z")

</div>

This sounds like a pretty low scale which a single RDS/Aurora instance would handle without a problem.

---

<div class="post-metadata">

**Author:** ![arjunraman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/arjunraman/32/865_2.png) [@arjunraman](https://community.temporal.io/u/arjunraman)\
**Post date:** [April 12, 2021, 11:23pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/3 "2021-04-12T23:23:45Z")

</div>

Sure. In case we find the load is higher than our initial calculation and we find Aurora is a bottleneck, we want to have fallback plans.

Is Vitess something which we can try today? Also, do you plan on supporting AWS Keyspaces?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [April 12, 2021, 11:26pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/4 "2021-04-12T23:26:03Z")

</div>

The last time we looked AWS Keyspaces didn’t support all the features of Cassandra needed for Temporal to run.

I believe Temporal DB schema is Vitess friendly. But we don’t have automated tests to validate Temporal releases against it.

---

<div class="post-metadata">

**Author:** ![arjunraman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/arjunraman/32/865_2.png) [@arjunraman](https://community.temporal.io/u/arjunraman)\
**Post date:** [April 12, 2021, 11:39pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/5 "2021-04-12T23:39:52Z")

</div>

Thanks for the details! Are there plans for Temporal to officially support Vitess in the future?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [April 12, 2021, 11:43pm UTC](https://community.temporal.io/t/support-for-vitess-amazon-keyspaces/1910/6 "2021-04-12T23:43:20Z")

</div>

We don’t have immediate plans, but we invested in making the DB schema Vitess friendly, so long term the support will be there.