3 ms·
does it actually work? Someone has to step forward and try it. You did that with tokyo and noticed it doesn't. Report your bug and after it's fixed it will wor
by moe 17y ago
does it actually work?
Someone has to step forward and try it. You did that with tokyo and noticed it doesn't. Report your bug and after it's fixed it will work better for the next person to try.
can anyone here vouch for a simple "plug and play" kv store that actually works as advertised
It doesn't exist. For the simple reason that most K/V stores are under 2 years old and haven't gotten enough real world exposure to work all the corner cases out.
If you want rock-solid then you're looking at the wrong market. Use PostgreSQL. It's not optimized for that use-case, but it's as chuck-norris as you'd expect after 20 years of development and production vetting. It won't segfault under load, it won't corrupt the datastore and it won't plot sawtooths while plowing through a large index.
And at the end of the day a K/V store is a table with two columns, right?
- gfodor 17y agoA few things. First, the "shoot the messenger" reply was inevitable, but doesn't really detract from my point that these types of blog posts trumpeting features and hype are not worthwhile. We will report this as a bug if and when we have a useful bug report to submit. As of right now we don't. Second, we use PostgreSQL for our RDMBSes -- I can't really say we've tried using it with the same use cases we'd be using for our K-V store and if it would work. We're talking tens of millions to hundreds of millions of HTML documents keyed by URL, and I'm skeptical the performance we'd get would be close to the 1000-10000 tps we experience with tokyo. Would be a good experiment, though!