
Exadra37
We have VMs, Containers and now I discovered Isolates
Cloudflare as workers to run serverless code without using containers:
So it seems that Isolates is based on:
What we ended up settling on was a technology built by the Google Chrome team to power the Javascript engine in that browser, V8: Isolates.
And they define Isolates as:
Isolates are lightweight contexts that group variables with the code allowed to mutate them. Most importantly, a single process can run hundreds or thousands of Isolates, seamlessly switching between them. They make it possible to run untrusted code from many different customers within a single operating system process. They’re designed to start very quickly (several had to start in your web browser just for you to load this web page), and to not allow one Isolate to access the memory of another.
We pay the overhead of a Javascript runtime once, and then are able to run essentially limitless scripts with almost no individual overhead. Any given Isolate can start around a hundred times faster than I can get a Node process to start on my machine. Even more importantly, they consume an order of magnitude less memory than that process.
Anyone knows more about the use of Isolates outside the use in the Browser and Cloudflare workers?
Am I missing any other technology as an alternative to VMs or containers? (other then the BEAM )
Most Liked

AstonJ
They certainly seem to be going in the right direction:
Though I have my doubts they will be as lightweight as BEAM processes…
(Maybe we need a thread for ‘alternatives to the BEAM’? :D)

Exadra37
The reply?:
Memory
The Node or Python runtimes were meant to be run by individual people on their own servers. They were never intended to be run in a multi-tenant environment with thousands of other people’s code and strict memory requirements. A basic Node Lambda running no real code consumes 35 MB of memory. When you can share the runtime between all of the Isolates as we do, that drops to around 3 MB.
and for startup time of a process:
Because Workers don’t have to start a process, Isolates start in 5 milliseconds, a duration which is imperceptible. Isolates similarly scale and deploy just as quickly, entirely eliminating this issue with existing Serverless technologies.
So 3MB is clearly much more memory needed than the KBs from the BEAM, and 5ms seems an eternity in the BEAM land as pointed out in the Elixir forum by @malaire:

dimitarvp
(Apologies, I’ll just copy-paste what I wrote in ElixirForum)
The only thing I am seeing in this idea is that somebody doesn’t seem to get the message that Javascript is not the future
“Stop trying to make JS happen. It’s not going to happen.” , as one meme goes.
The JS runtime is awful. As much as you try to fine-tune it it will inevitably spill its guts at the first sign of trouble. People spent weeks hand-crafting a Phoenix-like case for 1-2 million connections on a single server and it was a back-breaking work.
But that community doesn’t seem to be learning.
Popular General Dev topics
Other popular topics










Latest in Dev Chat
Latest (all)
Categories:
Popular Portals
- /elixir
- /rust
- /wasm
- /ruby
- /erlang
- /phoenix
- /keyboards
- /js
- /rails
- /python
- /security
- /go
- /swift
- /vim
- /clojure
- /java
- /haskell
- /emacs
- /svelte
- /onivim
- /typescript
- /crystal
- /c-plus-plus
- /tailwind
- /kotlin
- /gleam
- /react
- /flutter
- /elm
- /ocaml
- /vscode
- /opensuse
- /ash
- /centos
- /php
- /deepseek
- /scala
- /zig
- /html
- /debian
- /nixos
- /lisp
- /agda
- /sublime-text
- /textmate
- /react-native
- /kubuntu
- /arch-linux
- /revery
- /ubuntu
- /manjaro
- /django
- /spring
- /diversity
- /nodejs
- /lua
- /julia
- /slackware
- /c
- /neovim