You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hmmm after reading the blogpost, I don't think perfomance will be improved.
According the article : "What happens under the hood is that whenever you call JSON.SET, the module takes the value through a streaming lexer that parses the input JSON and builds tree data structure from it".
So, performance seems to be impacted : actually Nohm just store a blob of json (as string with JSON.stringify iirc), and this module parse & builds a tree data structure. I guess there is benefit when you need to walk in this structured JSON and seek for specific data, but it seems irrelevant in Nohm context.
Plus, it will require nohm to depend on it, which imply that everyone will need to have a minimum redis version (3.x ?) and build this module before using Nohm (or it will require large modification to detect the module and adapt code context according its presence).
I'm not the author of Nohm, so see it just as a personal feedback.
Redis has released a module for native JSON capabilities:
https://redislabs.com/blog/redis-as-a-json-store/
Would be nice to use this under the hood for the JSON data type?
The text was updated successfully, but these errors were encountered: