You have great points as far as application architecture is concerned. However, as far as server architecture goes - even if we separate the application into t

You have great points as far as application architecture is concerned. However, as far as server architecture goes - even if we separate the application into two different processes (HTTP and WebSockets), the current situation is that the WebSocket server in Ruby will run two IO reactors / "servers" internally (unless you use a custom WebSocket enabled server such as iodine). This post is more about the way WebSocket servers are implemented using Rack than about the question of application architecture.