Depending on what database you use you can do partial replication (only tables that aren't secrets) to a slave and then backup the slave. We use MySQL and that is possible. Also if you combine that with a high rotation…
Redis also support PubSub, lists, ordered lists, and hashes. Not exactly a strict "key value" store.
For perl it's fast as long as you have a small payload. Here's my benchmarks using progressively bigger data structures. perl: 5.008008 Storable: 2.21 JSON::XS: 2.25 Data::MessagePack: 0.34 ==== Size ====…
Since I use the RSS I only spend an hour at most a day reading stuff on here, but I work a ~40 hour week usually.
No. Each master has an offset so when you build a ring you give each master a different starting point. This keeps your ids in sync. So master1 would create ids: 1, 11, 21, 31, 41, 51, etc... and master2 would create…
Depending on what database you use you can do partial replication (only tables that aren't secrets) to a slave and then backup the slave. We use MySQL and that is possible. Also if you combine that with a high rotation…
Redis also support PubSub, lists, ordered lists, and hashes. Not exactly a strict "key value" store.
For perl it's fast as long as you have a small payload. Here's my benchmarks using progressively bigger data structures. perl: 5.008008 Storable: 2.21 JSON::XS: 2.25 Data::MessagePack: 0.34 ==== Size ====…
Since I use the RSS I only spend an hour at most a day reading stuff on here, but I work a ~40 hour week usually.
No. Each master has an offset so when you build a ring you give each master a different starting point. This keeps your ids in sync. So master1 would create ids: 1, 11, 21, 31, 41, 51, etc... and master2 would create…