Cloudflare acquires PartyKit to allow developers to build real-time multi-user
blog.cloudflare.com
blog.cloudflare.com
Or the company knew the deal was going forward and Cloudflare was unlikely to retain new employees?
Partykit is actually powered by Cloudflare Workers, so it's a compatible acquisition that adds realtime to the workers platform. Plus like you said they had recently and unfortunately "stripped PartyKit way back" with some layoffs, so I'd imagine the acquisition was fairly cheap for Cloudflare.
I'm biased but you should definitely try Triplit[2] if you want a super easy way to make real-time collaborative software that works seamlessly even when offline or on unreliable networks (like on mobile).
I'm a big fan of Cloudflare's openness, e.g., in supporting wasm in workers.
But I wonder if building lock-in is really in their customers' interests - or theirs, if people lose faith in them.
One of the value propositions for javascript+databases, and java before it, is that it was a programming model built in the open, and sometimes to standards that multiple vendors could supply. The openness of SQL has powered the industry, notwithstanding the manifold limitations and variants.
A PartyKit integration is not particularly concerning if it's just niche gaming, but if real-time collaboration really does become trivial to implement at the same time AI spreads into all corners of content, it could become the dominant programming model for emerging tech at scale. AI seems to have ample competition, but I see little competition and many barriers to entry for this kind of programming model.
People happily (or sometimes unhappily) lock themselves in with AWS since it’s convenient and useful. And that’s what Cloudflare is aiming to be in the serverless landscape even if it isn’t ideal.
Without reading too much of Partykit + Cloudflare, if you base your whole architecture on the way one company works and perhaps the pricing is too good to be true, you're setting yourself up for a rude shock in future.
Everytime I've looked at Cloudflare's pricing I've gone "that's bonkers cheap" for what you're getting, which sets off alarm bells that once a PE company gets their hands on it, it's not going to be that cheap any more.
But the Durable Objects API is not complicated and there's nothing stopping competing platforms from building a compatible product if they want. Much of the implementation is open source, even. In fact, if you build an app on DO but decide you don't want to host it on Cloudflare, you can self-host it on workerd:
(Which does seem to show off the lack of lag and responsiveness)
Not many people are currently on there, but you can just open another tab and see for yourself. Also has a little live chat which gets a bridge to their discord server, where you can chat with others that are currently on the page.
https://untested.sonnet.io/Sit.%2C+(together)+devlog+002+%E2...
Even with things like docs and sheets, though the capability is there, I find myself rarely editing in real time with others.
you could also build a 2-person permissive action link for nuclear weapons launches
or a stock exchange
If you're collaborating with other folks on a project, it's beneficial to see updates in realtime to maintain that one source of truth. Otherwise your work and theirs might overlap and someone will need to resolve merge conflicts. That, or you go the locking route, which comes with its own set of hassles.
[1] 3dverse.com
My SaaS day-job is a real-time multi-user checklist web-app - built using SignalR.
We're able to fit tens of thousands of concurrent users on a single Azure AppService instance - and we're self-hosted so we don't have IaaS-rug-pulling-anxiety - PartyKit looks cool, but I take a long-term view (5+ years) before adopting a technology, and PartyKit's brochure website is lacking information in that area...
SignalR's two main selling-points back-in-the-day (2014-ish) was its solid cross-browser support and how it abstracted over WebSockets, Comet, SSE, long-polling, et al - but it's 2024 now and everyone's on Chromium or WebKit, so cross-browser support is moot, and and WebSockets+SSE now covers all use-cases; so there's less going-for SignalR thesedays, and since the ASP.NET Core rewrite of SignalR it just doesn't scale as well on the client-side (as it no-longer multiplexes multiple Hub requests over a single connection, which is crazy... and HTTP/2+QUIC+3 doesn't really help, I find).
This press release was written by ChatGPT.
model = gpt4
prompt=write a press release for this announcement from cloudflare. Cloudflare acquires PartyKit to allow developers to build real-time multi-user applications
and guess what was halfway through...
"The acquisition of PartyKit by Cloudflare is more than just the merging of two technology companies; it is a significant leap forward in reducing the complexity and barriers to entry for developers aiming to build the next wave of interactive web applications. "
too good to be true
https://chat.openai.com/share/02976d40-f771-42ce-ae1e-738ba9...
I've seen lots of people get it wrong, claiming that something is ChatGPT when it isn't. To my understanding, this is because they are negative matching - "this sounds weird, so it must be AI", or "this is wrong, so it must be AI", and not positive matching on ChatGPTs exact tone.
ChatGPT being able to write this PR just shows how industry bog standard Cloudflare's PR is. It's like ChatGPT using the word "synergy".
I feel like an application like collaborative editing would send so much requests that billing would have to be insane, right? Even for my hobby size projects which I would like to publish for fun, terrify me with possible usage costs.
Their hibernation web socket thingy is great, but the real thing that scares me is the overall web socket message cost.
Oh and somehow I missed the Hibernation API announcement. Paying for idle but connected time is what made me nope out of trying it out.
Edit: Oh wow, I totally missed the rate limiter thing as well. Just last week I was implementing my own using DO. It's great to see this developments.
You still have to protect the DO through some sort of auth and/or rate limits.
Don’t see how any of these issues are unique to DOs.
If I have to think about batching messages to decrease costs even tho my overall transport and execution would be the same, I feel like that's an issue on the platform somehow.
Liveblocks also runs partly on Cloudflare Workers, it’s been great for stateful real-time servers.
While I might consider using Cloudflare, I wouldn't be willing to build an app in such a way as to depend on Cloudflare. If Cloudflare changes pricing, or comes under political pressure to terminate my account, or my business changes such that the Cloudflare offering is no longer suitable, I want a way to quickly migrate. It does seem that the main pieces are there and open source, but would likely require some amount of work to figure out and get into production.
PartyKit is open source (https://github.com/partykit/partykit/, MIT), so you could create your own back-end. The Socket.IO folks appear to have done this: https://blog.partykit.io/posts/party-io-a-socket-io-backend-...
... what a load of nonsense. I've built them in a few hours, spending £5 per month for a server.
More than that, isn't this precisely the kind of product that you would want operated by a large cloud infrastructure provider?