centrifuge VS Socket.io

BTW, Centrifugo is based on https://github.com/centrifugal/centrifuge Go library which may provide much more control and flexibility for Gophers than a standalone server and can be embedded to any Go app leveraging all Centrifugo client SDKs.

There are libraries which provide more advanced APIs for creating real-time applications, for example https://github.com/centrifugal/centrifuge

Yes, but there are two excelent libs for golang websockets - https://github.com/gobwas/ws - https://github.com/centrifugal/centrifuge

What https://github.com/centrifugal/centrifuge does:

Have you considered https://github.com/centrifugal/centrifuge? It also uses Gorilla WebSocket for WebSocket transport at the moment – but it's hidden inside and may be replaced if needed since Transport interface is pluggable. It's more heavyweight though than both Melody and Gorilla WebSocket but provides much more functionality out-of-the-box.

Not a Socket.IO compatible but maybe you will find it useful/interesting: https://github.com/centrifugal/centrifuge

Thanks! BTW, Centrifugo's core is based on https://github.com/centrifugal/centrifuge Go library - which theoretically can be more flexible and extensible solution for Go developers than Centrifugo server since server dictates some auth/permission/channel/api rules.

Hello, +1 to WebSockets. If you need to choose WS library – go with https://github.com/gorilla/websocket or https://github.com/gobwas/ws. You can also look at Centrifugo server (https://centrifugal.dev/, supports WebSocket, SockJS bidi transports, also EventSource, HTTP-streaming, GRPC unidirectional transports and many builtin features) or https://github.com/centrifugal/centrifuge Go library.

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

Nextjs + socket.io.. Planning to use webrtc for video calls later

Implementação em Node usando Socket.io

I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture.

yes. Im running on DreamCompute currently. Discord.js and socket.io within same app. A dedicated server works too, but pricier.

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).

For apps that require real-time communication, Socket.IO can be a valuable addition. It enables bidirectional, event-based communication between the server and client, making it an ideal choice for implementing real-time chat features.