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

add @primate/kv #124

Open
terrablue opened this issue Jun 8, 2024 · 2 comments
Open

add @primate/kv #124

terrablue opened this issue Jun 8, 2024 · 2 comments
Labels
modules modules / ecosystem
Milestone

Comments

@terrablue
Copy link
Contributor

terrablue commented Jun 8, 2024

@terrablue terrablue added the modules modules / ecosystem label Jun 8, 2024
@terrablue terrablue added this to the 0.33.0 milestone Jun 9, 2024
@gedw99
Copy link

gedw99 commented Jul 9, 2024

I use NATS KV because it's pure golang and cloud agnostic.

Its also reactive, so you can just change the KV value and all subscribers get it.

You can expose it over HTTP as a SSE for Browsers too, so that any Subscribers get the KV value over SSE. Here is a project that does that with HTMX. See:

https://github.com/delaneyj/datastar/blob/main/backends/go/site/routes_home.go#L152

https://github.com/delaneyj/datastar/blob/main/backends/go/site/routes_home.go

You can embed the server for local dev like this project does, and then for Prod use a NATS Cluster or Global Super Cluster.
https://docs.nats.io/running-a-nats-service/configuration/gateways

@terrablue terrablue changed the title support key-value stores add @primate/kv Jul 11, 2024
@terrablue
Copy link
Contributor Author

example in #137

@terrablue terrablue mentioned this issue Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
modules modules / ecosystem
Projects
None yet
Development

No branches or pull requests

2 participants