beehive
beehive copied to clipboard
Storage containers for Bees
Bees should be able to keep state with the help of local & global containers offering temporary & persistent storage.
Without these containers, restarting beehive implies restarting all bees as if they never run. Typically, my RSS to Twitter chain would re-emit tweets each time beehive is restarted
What would it take to expose a basic key/value store interface for the bees? We could even make it iterable since most Go key/value stores (bbolt, badger, etc..) all support map-reduce and prefix scans.
Perhaps only the bees that care about this interface (rss, email, etc..) would choose to use it. It could also simply be added manually to the bees that want it. I would assume having a separate database file for each bee would be ideal to help with manually "clearing the cache" unless we want to make it a UI option that handles that for us.