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

curious, when hot reload will be avail? #150

Open
kolinfluence opened this issue Oct 27, 2022 · 1 comment
Open

curious, when hot reload will be avail? #150

kolinfluence opened this issue Oct 27, 2022 · 1 comment

Comments

@kolinfluence
Copy link

great work!

  1. curious, when hot reload will be available?
  2. is it a good replacement for erlang after hot reload is available? (need websocket, telecom, fault tolenerant chat app kind of thing)
  3. how's the benchmark like against erlang?
@bkolobara
Copy link
Contributor

Hot reloading is always a pit tricky. The programming model needs to explicitly support it. In lunatic it will consist of 2 parts:

  1. Stuff inside the vm that lets you keep the process id and message queue, but replaces the code running.
  2. Higher level libraries that allows you to preserve state when the code is reloaded and potentially do state modification so that the newly loaded code can continue operating on the existing state.

This is fairly similar to how Erlang does it and I think it's a good approach for most use cases. However, currently we are stretched a bit thin and nobody is working on it. It's hard to predict when it will land.

To your other questions, I would say it's already a good replacement for some Erlang use cases. Lunatic should be faster in compute intensive workloads, but you would still need to benchmark to make sure it's actually faster :)

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

2 participants