NATS VS websocket

nats: Golang client for NATS, the cloud native messaging system

Install the nats.go package

Now that our NATS server is running, we'll be using Go and Node.js clients to connect to it for simple demonstration. Not familiar with Go or Node? Don't worry NATS has clients available in over 40 languages!

You can build monolith applications and if they need cross communication, rely on something like Nats: https://github.com/nats-io/nats.go

You could start by looking/reading how it is implemented in production ala https://github.com/nats-io/nats.go

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Also take a look at https://github.com/nhooyr/websocket - which is a good ws library, but I don't have anything specific about its memory usage per connection. But from what I see it will be somewhat similar to x/net/websocket.

nhooyr/websocket, shollz/pake, charmbracelet/bubbles, charmbracelet/bubbletea, charmbracelet/lipgloss, muesli/reflow, klauspost/pgzip and many, many more.

link: https://github.com/nhooyr/websocket

There's https://github.com/gobwas/ws and https://github.com/nhooyr/websocket but neither have seen a commit in over a year

The last time I was using websockets, I found https://github.com/gobwas/ws to be a huge improvement over Gorilla, but I haven't been looking recently, and perhaps Gorilla was able to shed some of its bloat and improve API and performance since then.