First time I've seen what appears to be a purely free project going on the offense against SaaS providers, complete with a mock pricing table. I wonder what the motivation is. Bad experience with a SaaS?
Brilliant website in any case. And I say this as someone who works on a realtime/push SaaS.
Anyway, what exactly is the use of this compared to just using uWS straight away? It’s build on uWS, so this is basically just a pusher implementation and some notification features with cool branding?
Yes, and what I replied earlier in this thread: I'm not the only one having this issue with overpriced Pusher, I just dont want to be limited by Pusher on how many messages I wanna distribute to my end users.
> Anyway, what exactly is the use of this compared to just using uWS straight away? It’s build on uWS, so this is basically just a pusher implementation and some notification features with cool branding?
uWS is cool to be used in any WebSocket client. However, Pusher has a strict protocol, so I wanted a product that works with any Pusher SDK - so I won't have to rely on custom clients or something of that ilk.
https://phoenixframework.org/blog/the-road-to-2-million-webs...
I think what they mean is it uses uWebSockets.js, a Node.js module wrapping a C++ implementation.
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 love FOSS, but the fact of the matter is that companies don't really care about FOSS. They care that the software they're using is working when they need it, and ultimately paying $49 a month is cheaper than owning or renting infrastructure AND paying someone to administer it in a way that works consistently, when they need it.
Saying "it is free" is true, but the man-hours you're now dedicating to hosting it, monitoring it, the network admin required, the time spent when it's not working, the single point of failure being moved from a datacenter to possibly an office building, the backup process, infratructure and administration, all of that costs money, and you get it all accounted for (and economies of scale cheaper) with SaaS. That is the single biggest reason SaaS is so popular with companies, with enough SaaS you can just rent an office and buy laptops, and only hire devs.
It’s used for things like notifying users when they get a DM, or displaying live sports scores.
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.
> Connections: Unlimited
> Messages: Unlimited
Yeah...there is still a limit to what a $5 instance can handle.
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.
But... but... Google are doing it!