3 ms·
I don't see this mentioned, but is KV.js used somewhere in production? Is there a recommended way to use it? For example in a separate worker, in a child proce
by omneity 4y ago
I don't see this mentioned, but is KV.js used somewhere in production? Is there a recommended way to use it?
For example in a separate worker, in a child process or in the same process as the node.js app, or embedded in an domain-specific server. Side note, is lua support in consideration? Some redis workloads rely heavily on it.
Looks cool and exhaustive nevertheless, the author did a great job!
- ent101 4y ago"I don't see this mentioned, but is KV.js used somewhere in production? " Hey, author here. It's used in puter.com, my startup. Still in alpha though. "For example in a separate worker, in a child process or in the same process as the node.js app," Right now I'd say in the same process as the node.js app. Open to suggestions. "Side note, is lua support in consideration?" Yes. "the author did a great job!" Thank you! Please do let me know how I could make it better :)
- pavlov 4y ago> "It's used in puter.com, my startup" Great domain, congratulations :)
- omneity 4y agoIn the past I needed something like redis, but in-process and “programmable from the outside”. I used Go libraries to do it then, but as I prefer JS/TS I’ll surely look at KV.js next time the need arises. Were you driven by any specific need/requirement while building KV.js?
- nine_k 4y agoRedis only uses Lua because Redis is written in C, and Lua is dynamic but has a good JIT compiler. For software written in JS, it would be natural to use another dynamic language with a good JIT compiler, namely JS again. I could see how introducing Lua might make sense if KV.js decided to be a faithful reimplementation of Redis's interface and (parts of) semantics, only in JS. Then dropping it in as a compatible replacement might be easier if Lua were supported, like in the original Redis.