3 ms·

Congrats on the launch! Glad to see more people working on these kinds of problems. As someone who hasn't built one of these systems before... What does Razorf

Congrats on the launch! Glad to see more people working on these kinds of problems. As someone who hasn't built one of these systems before... What does Razorfish give you that running Socket.io as a separate microservice that talks to your existing API service over an existing message queue doesn't? Is it for people with architectures that don't have an existing queuing or API services already? Or does it handle sharding the Socket.io part easily which usually has to be vertically scaled? (Sorry if these questions don't make sense, I haven't dug into my requirements for these things yet but I know they're coming up!) I think a very clear explanation of that would help me (and maybe others) understand its value and how hard it would be to roll your own here.

edshpark 10y ago
Hey Ian - this is Edward, one of the co-creators of Razorframe. Thanks for your thought provoking question! Developers can certainly utilize the architecture you've described to great effect, but our solution aims to deliver a lightweight option that integrates technologies that don't normally play nice (Socket.io and clustered Node instances) but can have awesome scaling potential when they do. By keeping all the features within a familiar environment in Node, we've experienced that development time was vastly reduced in a potential project that expected a high volume of Websocket communications. For example, the incorporation of an in-memory queue reduces the need for developers to incorporate an external piece of tech (and any new language adoption) into their Node.js projects