This ain't new. Any language supporting loading modules can give you the organization benefit of microservices (if you consider it a benefit that is - very few orgs actually benefit from the separation) while operating like a monolith. Java could do it 20+ years ago, just upload your .WAR files to an application server.
Erlang could do it almost 40 years ago.
It can be used to upgrade applications at runtime without stopping the service. That works well in Erlang, it’s designed from the ground up for it. I know of a few places that used that feature.
It might see the light of day at some point in the future, but if the past is anything to go by...
Small teams, big results is a characteristic that I’m very interested in, in our post-ZIRP reality.
But they're the only real case studies
If I were to say "Go", people can point to big projects like Docker, Kubernetes, etcd, Googles internal use, and a few others (Uber?)
Erlang just doesn't have that sort of buy in, which is concerning because it's been around longer than Go (as a FOSS language), heck it's been around longer than Python (but it was proprietary back then)
Speaking as someone that's never used it, that's got "don't bother unless you've got an academic interest in it" written all over it
So it remains a “secret” weapon and I am fine with that. Not everything have to be validated by popularity in order to be unreasonably effective.
Whatsapp is implemented with Erlang.
It is a more robust platform for agentic AI, and I’d certainly start with a BEAM language for agentic AI.
Besides: Erlang predates Java.
NGL It was clever enough that every few years I think about trying to redo the concept in another language....