You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i know they are similar to each other, and i think the design is superior to boltdb, but why did couchbase and bleve, etc go with bolt over this ?
i guess there were reasons, and i am a bit curious what they were.
I am asking because i am looking for a kv store.
i have written a tool to convert map reduce computations such that you can write it in standard golang, parse the AST, and produce a distributed CFG (computation flow graph). Hence allowing a computation to meet its SLA, by throwing more hardware at it.
Now, for each node (process or server), i need a backing store because each needs some memory / file store for long running computations. Bring the computation to the data way of thinking.
Its for machine learning type event sourcing.
The text was updated successfully, but these errors were encountered:
I'd also be interested in knowing what the comparison is? Or, why this looks pretty awesome but there hasn't been much happening recently. Is it because it's technically not going anywhere, because of lack of uptake or something else?
i know they are similar to each other, and i think the design is superior to boltdb, but why did couchbase and bleve, etc go with bolt over this ?
i guess there were reasons, and i am a bit curious what they were.
I am asking because i am looking for a kv store.
i have written a tool to convert map reduce computations such that you can write it in standard golang, parse the AST, and produce a distributed CFG (computation flow graph). Hence allowing a computation to meet its SLA, by throwing more hardware at it.
Now, for each node (process or server), i need a backing store because each needs some memory / file store for long running computations. Bring the computation to the data way of thinking.
Its for machine learning type event sourcing.
The text was updated successfully, but these errors were encountered: