I see ActorCore as picking up on PartyKits vision where they left off after acquisition by Cloudflare. Here's a few of the few things we've added to ActorCore:
- Full TypeScript type safety for calling actions on actors – PartyKit provides raw WebSocket messages instead
- Streamlined state persistence – PartyKit requires using low-level storage calls for persistence
- Flexible scheduling API – PartyKit exposes the single alarm from Cloudflare instead
- Simpler "functional" API – you might prefer PartyKit if you prefer using ES6 classes
- Upcoming SQLite features & deep integrations for features like auth & local-first sync will make it easier to ship quickly
- Not vendor-locked to Cloudflare
PartyKit already has a few integrations that is on our roadmap, such as Yjs
> I don't quite get the concept yet. The details are kinda slim.
Would be helpful to learn more. From looking at one of the examples, can you elaborate a bit on what doesn't make sense? Or is this more broadly how it works architecturally?
> That link appears broken.
Looks like we had a broken link in the mobile nav – is that where you found it?
I've wanted something like this for a long time, going to take it for a spin. Looks like there is a lot of help wanted on certain underlying implementations so that would be fun to help out with too.
I think there is tremendous value in having these functions that appear stateless and run in "stateless" environments like aws lambda, but on each invocation they are handed the previous state and are able to augment it and return (to persist) or do nothing.
There’s definitely a lot of inspiration from Erlang. We’re far from the first actor-ish framework, but we’re hoping ActorCore sticks by working seamlessly with existing tools, instead of forcing people to learn a new paradigm.
We’re open to contributions – feel free to join our Discord if you have questions.
Hey Nathan, cool project and thanks for sharing.
I've tinkered with Actor Core a bit but need to play with it more.
How would you compare/sell it to someone who uses or is familiar with https://partykit.io/
Appreciate the kind words!
I see ActorCore as picking up on PartyKits vision where they left off after acquisition by Cloudflare. Here's a few of the few things we've added to ActorCore:
- Full TypeScript type safety for calling actions on actors – PartyKit provides raw WebSocket messages instead
- Streamlined state persistence – PartyKit requires using low-level storage calls for persistence
- Flexible scheduling API – PartyKit exposes the single alarm from Cloudflare instead
- Simpler "functional" API – you might prefer PartyKit if you prefer using ES6 classes
- Upcoming SQLite features & deep integrations for features like auth & local-first sync will make it easier to ship quickly
- Not vendor-locked to Cloudflare
PartyKit already has a few integrations that is on our roadmap, such as Yjs
Curious to hear your experience using both.
https://rivet.gg/docs/general
That link appears broken.
I don't quite get the concept yet. The details are kinda slim.
> I don't quite get the concept yet. The details are kinda slim.
Would be helpful to learn more. From looking at one of the examples, can you elaborate a bit on what doesn't make sense? Or is this more broadly how it works architecturally?
> That link appears broken.
Looks like we had a broken link in the mobile nav – is that where you found it?
Mobile, yes.
Perhaps a use case?
To say it's like another service requires me to know the alternative and now your completion is known as well.
I'm also curious how the service handles multiple requests to the same state.
Does this example list help? https://github.com/rivet-gg/actor-core?tab=readme-ov-file#ex...
> I'm also curious how the service handles multiple requests to the same state.
That's the key part of ActorCore – state is persisted across requests. It's like a Lambda function that can (a) run forever and (b) persist state.
Congrats on the launch! Glad someone is building this.
Thanks Paul
ActorCore is awesome. Stateful Serverless is the future!
Thank you!
I've wanted something like this for a long time, going to take it for a spin. Looks like there is a lot of help wanted on certain underlying implementations so that would be fun to help out with too.
I think there is tremendous value in having these functions that appear stateless and run in "stateless" environments like aws lambda, but on each invocation they are handed the previous state and are able to augment it and return (to persist) or do nothing.
Very erlang-y, which is rad.
Appreciate the kind words!
There’s definitely a lot of inspiration from Erlang. We’re far from the first actor-ish framework, but we’re hoping ActorCore sticks by working seamlessly with existing tools, instead of forcing people to learn a new paradigm.
We’re open to contributions – feel free to join our Discord if you have questions.