Want to contribute socket.io adapter implemented with NATS.io #4216
-
| 
         Thanks for such a nice project  And I have reached to an limitation of building high-availability messaging system since redis single machine is bottleneck of the architecture. I considered redis-cluster to get rid of the problem, but it was unsuccessful to meet my requirement (1) easily auto-scalable and (2) well maintained messaging system client. In the midst of these concerns, I found NATS.io to alternate redis. Now I am building socket.io-adapter using NATS.io as messaging service. 
 The project probably be finished within this month, and I want to share the result with the community. Is there a process for sharing project to socket.io community?  | 
  
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
| 
         That's great, thanks! I think we could list it in the adapter section here: https://socket.io/docs/v4/adapter/ You can also take a look at https://github.com/MickL/socket.io-nats-adapter, for reference.  | 
  
Beta Was this translation helpful? Give feedback.
That's great, thanks! I think we could list it in the adapter section here: https://socket.io/docs/v4/adapter/
You can also take a look at https://github.com/MickL/socket.io-nats-adapter, for reference.