Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Actor Model? Erlang / BEAM #6

Open
mikecann opened this issue Nov 18, 2021 · 0 comments
Open

[Discussion] Actor Model? Erlang / BEAM #6

mikecann opened this issue Nov 18, 2021 · 0 comments

Comments

@mikecann
Copy link

mikecann commented Nov 18, 2021

For a long while I have been jealous of Erlang's scale and tooling for monitoring, upgrading running systems and tolerance for crashes.

What has held me back really is the language (I would miss my types too much :P)

Since I first heard about Durable Objects I was excited as it sounded like the Actor model and it had me wondering; would it be possible to finally implement a proper serverless actor system using web languages and tooling?

Before experimenting with that; I wanted to scratch and itch for the summer dev challenge.

With that out of the way I got back to thinking about Actors and how it might be done. I came across this example on denoflare that showed that inter-DO sockets were possible. So now I know that I knew it must be possible to build a fan-out cluster of nodes that all talk to each other.

Then I came across this repo and have been mightily impressed. I think its exactly what you need for a foundation towards a proper Actor system.

What are your thoughts and plans long term for this library? What do you (and Cloudflare in general) think about Actor model on DO / Workers?

As a thought exercise how would you go about scaling the chat example from this repo up to handle 5,000,000 concurrent users?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant