What can I use it for? What is it?
It’s used for things like notifying users when they get a DM, or displaying live sports scores.
31–40 of 40 posts
What can I use it for? What is it?
It’s used for things like notifying users when they get a DM, or displaying live sports scores.
Earlier quoted context omitted.
That 5$ instance will cover 90% of the needs of 90% of the businesses out there. You. Are. Not. Google/Facebook/Netflix/TikTok.
> You. Are. Not. Google/Facebook/Netflix/TikTok. That cannot be repeated enough. 90% of the tech flaunted here on HN is interesting only on a technical level, never in a business setting. I suspect Google released Kubernetes to hamstring all competition. You do not need it. Unless you're Google.
So it’s overkill for a CRUD app, but you certainly don’t need the scale of Google to find it useful.
> Written on top of C, ported to Node.js. I think what they mean is it uses uWebSockets.js, a Node.js module wrapping a C++ implementation. https://github.com/uNetworking/uWebSockets.js
Its a STOMP protocol server written in non-blocking C. +web sockets.
There is no code required in the nginx part because it implements stomp topics and queues. If you want code, it plugs into a rust based stomp server talking reverse STOMP protocol, so you can code all you like in rust and scale out with n x nginx servers.
It is very very low on cpu use. I wrote it because rabbitmq used 5% cpu while idle. Xtomp uses close to 0% cpu when idle because nginx.
I'm a php & mysql -dev and still can't understand these websockets. What if I have a cron job that sends messages to this websocket server and it pushes them to web-app (vue front, added to home screen on mobile phone, not an installed app) push notification. How this can be done ? and how can the server even keep up with the websocket connections to thousands of clients ? does the websocket re-open if user restarts…
Oof Ably not looking so good suddenly..
Also they come with reliable message delivery built in (pusher doesn’t I think). Not really sure how it compares to this project.
Anyways just a happy user of ably, used it at work.
Earlier quoted context omitted.
The creator of Soketi here. Even if I have 50-100 concurrent connections on most of the projects, I don't wanna be throttled by how many messages I can distribute to my end users - I might have < 100 users, but maybe I have to distribute fresh updates each 5 seconds, what do I do?
You use a stack which supports it. Elixir and Erlang support millions of concurrent websocket connections on a single, albeit beefy, server. https://phoenixframework.org/blog/the-road-to-2-million-webs...
> Written on top of C, ported to Node.js. I think what they mean is it uses uWebSockets.js, a Node.js module wrapping a C++ implementation. https://github.com/uNetworking/uWebSockets.js
If you want a really fast cheap websockets server that scales to 250,000 cc on a single node, I wrote xtomp.tp23.org using nginx as a base. Its a STOMP protocol server written in non-blocking C. +web sockets. There is no code required in the nginx part because it implements stomp topics and queues. If you want code, it plugs into a rust based stomp server talking reverse STOMP protocol, so you can code all you like i…
Earlier quoted context omitted.
The library is built on top of uWebsockets which is fairly well-known as being highly optimised and performant, especially if you skip the Node.js wrapper and use the underlying C/C++ lib directly. Does anyone know what tradeoffs or different performance characteristics one would expect to see from e.g. Elixir/Erlang vs uWebsockets?
Elixir/Erlang are surely slower but the BEAM is a fantastic runtime and compensates with fault-tolerance and predictable performance. I know I prefer my server to be as responsive at 1 million connections as at 1 hundred.
Earlier quoted context omitted.
That 5$ instance will cover 90% of the needs of 90% of the businesses out there. You. Are. Not. Google/Facebook/Netflix/TikTok.
> You. Are. Not. Google/Facebook/Netflix/TikTok. That cannot be repeated enough. 90% of the tech flaunted here on HN is interesting only on a technical level, never in a business setting. I suspect Google released Kubernetes to hamstring all competition. You do not need it. Unless you're Google.