4 ms·
Here's an orthogonal thought. Kubernetes is really popular, but it really should've been Erlang or some other kind of distributed Smalltalk that vaguely smells
by elvinyung 8y ago
Here's an orthogonal thought. Kubernetes is really popular, but it really should've been Erlang or some other kind of distributed Smalltalk that vaguely smells like serverless. Distributed objects failed originally because RPC was a leaky abstraction.
The idea of a "server" at this point, then, is basically an extremely coarse-grained unit of work and locality. You deploy some binary onto a box on a rack, you ensure that the stuff on the binary stays together in one place.
But what we really care about is objects and functions/methods, and having related objects be closer together. In the ideal world, we should just be able to throw more and more machines at a cluster, and have it transparently rebalance objects underneath, taking into account load and affinity.
- scroot 8y agoOne of the more important ideas here is that you have to simulate time within your Actors/Objects [1]. There is so much possibility here, but since the status quo more or less "works" in market terms, it's hard to push for anything better. [1] https://oneofus.la/have-emacs-will-hack/files/2005_Teatime_Framework_Design.pdf https://oneofus.la/have-emacs-will-hack/files/2005_Teatime_F...