1. I speak fluently C++ and learning Rust would take me years. 2. Foodchain of libraries that I am intimately fimiliar with in C++ and I am not familiar with in Rust. Take Rust Tokyo, for example. This is the de facto the standard for how to build I/O backends. However if you benchmark Tokyo's min-redis with memtier_benchmark you will see it has much lower throughput than helio and much higher latency. (At least this is what I observed a year ago). Tokyo is a combination of myriad design decisions that authors of the framework had to do to serve the mainstream of use-cases. helio is opinionated. DF is opinionated. Shared-nothing architecture is not for everyone. But if you master it - it's invincible. (and yeah - there is zero chance I could write something like helio in Rust)...
Re:Dragonflydb – A modern replacement for Redis and Memcached
by dragosbulugean on Monday May 30, 2022 @02:51PM
(#31562297)
would love to hear why c++
[ Parent
| on HN ]
Re:Dragonflydb – A modern replacement for Redis and Memcached
by romange on Monday May 30, 2022 @03:37PM
(#31562796)
If I would choose another language it would be Rust. Why I did not choose Rust?
Re:Dragonflydb – A modern replacement for Redis and Memcached
by jen20 on Monday May 30, 2022 @05:56PM
(#31564058)
Tokio is not a shared-nothing model - you’d be looking at Glommio [1] (from one of the contributors to Seastar) for that.
Re:Dragonflydb – A modern replacement for Redis and Memcached
by infamouscow on Monday May 30, 2022 @03:30PM
(#31562722)
The deal breaker for me was stable Rust doesn't have fast thread locals[1] nor stack probes for arm64[2].