We have a requirements for running Temporal on AWS using a NoSQL data persistence layer (ideally serverless). Here’s a review of the options as I understand them:
- AWS KeySpaces: not currently supported due to AWS KeySpaces limitations.
- Mentioned here as a possible option: temporal/persistence.md at c16eef677d7cec244c6093d0749ba745a958d8fd · temporalio/temporal · GitHub but it’s unclear to me if this is a valid statement.
- In DynamoDB persistence driver · Issue #684 · temporalio/temporal · GitHub Samar Abbas states that running Temporal using DynamoDB is not possible due to DynamoDB’s transaction size limitations. Not sure what he’s referring to by ‘size’, but since his comment, DynamoDB’s transaction sizes have increased to a maximum of 100 unique items. (and a max of 4MB of data). Service, account, and table quotas in Amazon DynamoDB - Amazon DynamoDB
- In Temporal consistency guarantees tradeoffs, Maxim states that a Redis backend should be technically possible.
Is anyone aware of any missing potential option?
What would be a suitable path forward for us? We could be open to implementing and contributing a persistence backend to Temporal for this requirement.