While of course I appreciate the ingenuity here...at what point does doing something like this with node just become trying to force a square peg into a round h

While of course I appreciate the ingenuity here...at what point does doing something like this with node just become trying to force a square peg into a round hole? Node is great for squeezing performance out of a box saddled with io bound tasks, or handling a large number of mostly discrete connections, that don't share a ton of state. If you need access to something like a cache where synchronization is not a major issue, and you don't want to dupe memory across the processes, you can throw something like redis on the box. However, if what you really want shared memory across what are now essentially threads...why wouldn't you go to a technology that's been designed for the task? I'm referring to the likes of Java, Scala, golang, etc.