-
Notifications
You must be signed in to change notification settings - Fork 1
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
Clustering #18
Comments
This is a future goal. One obstacle would be the interplay between the storm ORM (which uses a boltdb fork) and any such raft library. Our data access is simple enough that we could switch to a lower-level key-value lookup without too much trouble. |
ah interesting. I did not know storm uses a fork of boltdb. I guess etcd or consul then later... Shall i close this now ? |
We can leave this open as a stake in the ground for the feature itself. I would be down to run experimental branches of storm that support this, or perhaps integrate things manually with a generic raft library. |
Yeah i saw that storm is being rearchitected but i really doubt storm will ever get clustering. ! Its also much better than consul and plenty of example for using it as a low transaction DB. You also will get real time push, so when when a value changes it will automatically update the proxy. As it say on their web page is stored more than a few GB of data use CockroachDB. So food for thought... I am only thinking through an easy way to get HA and fast development. |
Not sure if co-chair does this but what about clustering using boltdb raft ?
That is how consul do it but since you want a very simple system you can just use one of the boltdb raft libraries.
The text was updated successfully, but these errors were encountered: