Key/Value storage functionality #34

Closed
opened 2018-08-26 08:07:10 +00:00 by jamie · 4 comments
jamie commented 2018-08-26 08:07:10 +00:00 (Migrated from git.hazaar.io)

I can't believe I haven't come up with as yet, but I think it would be cool to leverage the Hazaar protocol and Warlock to use it as a key/value storage system, similar to Redis.

This will mean that later, when warlock replication is enabled, I will be able to implement a replicated key/value storage system. Having this as a feature may even make that more of a priority.

I can't believe I haven't come up with as yet, but I think it would be cool to leverage the Hazaar protocol and Warlock to use it as a key/value storage system, similar to Redis. This will mean that later, when warlock replication is enabled, I will be able to implement a replicated key/value storage system. Having this as a feature may even make that more of a priority.
jamie commented 2018-08-26 12:22:00 +00:00 (Migrated from git.hazaar.io)
created branch [`34-key-value-storage-functionality`](https://git.hazaarlabs.com/hazaar/hazaar-warlock/compare/master...34-key-value-storage-functionality)
jamie commented 2018-08-26 12:22:01 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !13

mentioned in merge request !13
jamie commented 2018-08-26 14:01:55 +00:00 (Migrated from git.hazaar.io)

closed via merge request !13

closed via merge request !13
jamie commented 2018-08-26 14:01:55 +00:00 (Migrated from git.hazaar.io)

closed via commit c3476d674f

closed via commit c3476d674fc33ae8ae23d7b371dea581d6362bc8
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#34
No description provided.