Closed morlinbrot closed 8 months ago
I would love to contribute to this, is it okay if I pick this issue?
Hi @KaviiSuri, as mentioned in the OP, i'm currently working on adding SQLite support to shuttle, I think it would be worth waiting for that to land before starting work on this one.
Also, I think there is some deliberation by the Shuttle team needed before we can get started here, esp. for figuring out how this would relate to shuttle-persist
and which engine should be used to power the functionality.
No issues! Really excited about the project, feel free to let me know if there's anything I can contribute to!
Closing in favour of #1567 #1565 #1321
Describe the feature
Both Deno and Vercel recently added a KV Store to their offering which I believe would be a very useful option for Shuttle too, especially in the context of
shuttle-next
. A simple, built-in KV Store API goes a long way in enabling spinning up a web application quickly and would go a long way in making onboarding to Shuttle very easy, IMHO.I do realise that there is
shuttle-persist
already but I think backing this with a proper db engine would make it more durable and portable. In this context, this request could be regarded as an upgrade to the existingshuttle-persist
.The above mentioned services use different engines to provide the functionality, afaik:
We are currently in the process of adding SQLite support, and having Redis support will probably also be a great feature to have in the future, too. In any case, I think a simpler, built-in KV Store abstraction would be a nice addition, especially for attracting new users to Shuttle.
Let me know what you think, I'd be glad to spend some time on this after adding the SQLite support.
Suggestion or Example of how the feature would be used
I love the simplicity of Deno's KV API so here's an adaptation of that plus the existing persist example:
Duplicate declaration