Jamsocket: Back Ends for Realtime Apps • Hacker News Board

Re: Jamsocket: Back Ends for Realtime Apps

#41

Post by stunt » Thu, Jun 22, 2023, 9:23 PM UTC

paulgb wrote: post #7

Hey HN! I'm a co-founder of Jamsocket, happy to answer any questions. We've previously been on HN for Plane, which is the open-source engine behind Jamsocket. https://news.ycombinator.com/item?id=33178797 Sorry for the website performance issues, I've disabled the animation which should help.

The session thing looks really cool, but when do I need it? I can develop a simple real-time app using socket.io or a service like Pusher.

Why would I choose this instead? That isn't clear to me yet.

Re: Jamsocket: Back Ends for Realtime Apps

#42

Post by veryvisa » Thu, Jun 22, 2023, 11:10 PM UTC

I'm unable to view https://github.com/drifting-in-space/jamsocket-nextjs-tutori...

Re: Jamsocket: Back Ends for Realtime Apps

#43

Post by paulgb » Thu, Jun 22, 2023, 11:38 PM UTC

veryvisa wrote: post #42

I'm unable to view https://github.com/drifting-in-space/jamsocket-nextjs-tutori...

Thanks for letting us know — it’s fixed now!

Re: Jamsocket: Back Ends for Realtime Apps

#44

Post by paulgb » Fri, Jun 23, 2023, 12:12 AM UTC

stunt wrote: post #41

paulgb wrote: post #7

Hey HN! I'm a co-founder of Jamsocket, happy to answer any questions. We've previously been on HN for Plane, which is the open-source engine behind Jamsocket. https://news.ycombinator.com/item?id=33178797 Sorry for the website performance issues, I've disabled the animation which should help.

The session thing looks really cool, but when do I need it? I can develop a simple real-time app using socket.io or a service like Pusher. Why would I choose this instead? That isn't clear to me yet.

If you write a socket.io service that uses broadcast, and then scale up to more than one server, your users will be split between those servers and won’t be broadcast to the other. Jamsocket allows you to generate a unique hostname for each room that ensures that every user is talking to the same server. That server can still use socket.io in addition to Jamsocket; they work at different layers of the stack.

Pusher solves the problem of scaling in a different way, which is by giving you an HTTP endpoint to send events to. It’s better for large broadcast groups (e.g. sending people sports scores) but doesn’t run any compute for you.