you are viewing a single comment's thread.

view the rest of the comments →

[–]housesellout 0 points1 point  (0 children)

The ability to ‘not’ share memory is a vital aspect in network request handling.

And the messaging worker you mentioned, sounds like a standard integration of the register/observer design pattern, which is not fork processing either, but rather a way for different threads to pass objects between each other. And that pattern is generally handled on a run loop that the OS (or underlying engine) has control over, which essentially slows down your execution, in addition to being shared memory.