Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] New architectural proposal for the Statestore #365

Closed
sleipnir opened this issue Sep 3, 2024 · 0 comments · Fixed by #368
Closed

[Feat] New architectural proposal for the Statestore #365

sleipnir opened this issue Sep 3, 2024 · 0 comments · Fixed by #368
Assignees
Labels
enhancement New feature or request proxy sdks Support languages statestores
Milestone

Comments

@sleipnir
Copy link
Member

sleipnir commented Sep 3, 2024

Describe the feature
I propose using Nats as the primary source of persistence, or in other words as a source of storage for hot data. And using relational databases as a secondary source for storing cold data that has already expired ttl.

Why would that be important to you?
It allows you to more easily implement other types of flows such as Projections and collection types.

Additional context

statestore-archictecture

Details:

statestore-arch-details

@sleipnir sleipnir added enhancement New feature or request statestores proxy sdks Support languages labels Sep 3, 2024
@sleipnir sleipnir moved this to In Progress in Spawn v1.5.0 Sep 19, 2024
@sleipnir sleipnir added this to the 1.5.0 milestone Sep 19, 2024
@sleipnir sleipnir linked a pull request Sep 20, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Done in Spawn v1.5.0 Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request proxy sdks Support languages statestores
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants