&gt;  to get the benefits of shared nothing, &quot;green thread&quot;&#x2F;&quot;VM internal processes&quot; ... Stackless Python<p>It is shared everything isn&#x27;t it. Greenlet is core which was extracted out of stackless and both gevent and eventlet are based on it. Can get lightweight concurrency units sure. That&#x27;s very far from Erlang.<p>To put it another way a thread (even a green one) + a thread safe queue does not an Erlang make ;-)<p>But is a popular trope usually, when frameworks claim &quot;we do Erlang&quot; it often means that.<p>Some of the things Erlang has can be found in various languages and frameworks. The best approximation is actually -- an operating system. OS processes are closest to how Erlang works. They are isolated from each other. Can have systemd or other things supervise them. Can send messages via pipes, unix sockets, files etc. But can&#x27;t have 1M of those running.<p>Then like you mentioned can have green threads in other languages. But can&#x27;t have low latency GC, CPU scaling, isolated memory for each concurrency unit. So not quite there.<p>&gt; The Pulsar framework- <a href="https:&#x2F;&#x2F;pythonhosted.org&#x2F;pulsar&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pythonhosted.org&#x2F;pulsar&#x2F;</a><p>That does look pretty cool. I&#x27;ll have to take a look. Thanks for the link!