GitHub user git-hulk edited a comment on the discussion: Difference between kvrocks and pika
It's a good question, many users should have the same confusion, I would try to explain the differences, but it's only my objective thoughts and can't promise fairness. **From the key design:** * We prefer to keep consistent with Redis sematic which the Pika didn't. e.g. Pika allows different types to have the same key which wasn't expected. * We do much work on improving the performance and decreasing the latency. Like auto adjust the block and SST with the key-value size, as well as using the compaction checker to reduce the full compaction on the RocksDB. * More features were supported by Kvrocks, like Lua and Transaction * We also care about profiling which would help users to find the performance issue. Users can use the `perf` command to investigate the issue when suffering the latency spike. * Finally, the core competitiveness of the kvrocks was simple and maintainable enough for most users. The tendis should be too complex for most users/companies, and also hard to deploy. **From the organization:** Kvrocks has been denoted to the Apache incubator now, so it didn't belong to any companies or organizations. Also, core team members were from different companies with many years in the distributed key-value field. GitHub link: https://github.com/apache/incubator-kvrocks/discussions/319#discussioncomment-926025 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
