Is there any paper describing the concepts behind this project ? Is this seems very similar in its goals from the OTP architecture (from a distance), i’m curious to understand more about the first principles that guides the design.
"Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang."
They do tag their project as "actor-model" so there is some similarity. However I see their communication model is designed to be more protocol agnostic.
Funny thing is that a distributed, resilient, asynchronous message passing program in Erlang, is their equivalent of a "Hello World". It's so natural, and so well baked into the runtime itself, that it's hard to do something different.
Good for the SwimOS folks to keep working in this important space, but I would have expected at least some mention of Erlang/OTP in their site, if nothing else, to understand the difference in approaches.
More (and clearer) documentation coming very soon, but here's a good start for the basic SwimOS concepts (Web Agents, Lanes, and Links): https://www.swimos.org/concepts/
Open Telecom protocol....the name is basically meaningless but I'm guessing ericson had no way of know how genetically useful it would end up being at the time.
Looks very cool, and I bet it works great, but that is a lot of technology stack to learn, adopt, and trust to solve all my problems without being too complicated.
I feel like user adoption will be hard earned because it is such an integrated and new solution.
Scale and performance and the primary benefits of the SwimOS architecture. We've run the entire traffic.swim.ai application (monitoring real-time events from traffic infrastructure) for the City of Palo Alto, CA on a Raspberry Pi, for demo purposes. Most apps we use SwimOS for are at the scale millions/events/second and distributed across many machines.
@skyde SwimOS apps are interconnected graphs of Web Agents (stateful objects that persist relevant state locally). They subscribe to peers via streaming links to receive event updates in real-time. You can read more about Web Agents here (https://github.com/swimos/swim) and here https://www.swimos.org/concepts/agents/
