4 ms·
My hope is that the modules will be used more for common use cases (leaderboards, real-time counters, etc) instead of turning into gem dependency hell. Having a
by fzsix 10y ago
My hope is that the modules will be used more for common use cases (leaderboards, real-time counters, etc) instead of turning into gem dependency hell. Having a community backed module for a single purpose in that regard sounds pretty good, and the fact that they are written in C should filter out devs that follow a higher level dependency model as raw performance is a key metric.
- jasonjei 10y agoI agree. I think Sidekiq is a good example of how modules are used. You can add the Pro features, use a community plugin, but the plugins usually don't affect core functionality (such as the Sidekiq "cron" scheduler, error reporting options, etc). I think C is both a blessing and a curse. The challenge of using C correctly has led to memory leaks, remote code execution, segfaults, etc. I'd use Go if it's possible to write Redis modules.
- PeCaN 10y agoYou could use C++, Ada, or Rust if you use the right pragmas. I don't use Go but I'd be surprised if it can't export C ABI compatible functions somehow.
- tyho 10y agoIt is possible to make Go redis modules since go 1.5 thanks to the c-shared buildmode, I would be surprised if there wasn't a go package to make it easy within the month.
- dvirsky 10y agoI was planning on writing a Go module wrapper but didn't get to it before RedisConf. I'm more interested though to see when a JS module wrapper gets implemented.