Thanks for the feedback and support! We have added unit tests this morning and will continue to add more. Also, we have been using Artillery.io for load testing to measure the performance gains from multiple Node workers and the linked-list messaging queue.
Nothing happens to items in the queue in such a case. New workers will automatically respawn, and the adapter that links all the workers on the back-end will re-attach to newly spawned workers. Clients formerly connected to workers that are now gone will have to re-attach to new workers by socket.io.
Hey, it's Travis, one of the co-creators of Razorframe... Firebase is a paid platform-as-a-service that includes realtime database hosting (what it's primarily known for) as well as numerous other services such as app analytics and hosting. It's a great platform and we definitely drew inspiration from them.
Razorframe, on the other hand, is an open-source project that addresses 2 of the main trends we see in modern web applications: real-time client UIs and flexible server-side scaling. We built a Node module that you can bring into your server-side code to quickly get up and running with websockets (via socket.io) and Node clusters in order to accomplish both.
Check us out on GitHub and let us know what you think:)