[Bro-Dev] Broker data store API
vallentin at icir.org
Mon Jul 25 08:25:07 PDT 2016
> I can't speak to whether or not it is 'needed', but I have had desire
> to use it in the past... The only thing preventing me from doing it
> was the fact that Broker is currently a fast moving target.
Good to know. Scott Campbell also uses the current version of Broker in
his projects and mentioned the need for a scalable and performing
> Generally speaking, I was wanting to do it so that I could save state
> between cluster restarts (specifically for authentication data).
How many keys to you anticipate in your data store? And what's the rate
of updates? Any ballpark estimate would be useful here.
Given the interest in a scalable backend, I will bring back support for
a RocksDB backend.
More information about the bro-dev