SwimOS: Distributed platform for building stateful, real-time streaming apps
1–10 of 16 posts
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#2This is super cool!
I’ve been idly thinking about something like this for a while so it’s cool to see it actually exists.
Has anyone used this? If so what’s it like, performance and ease of use? Are there any similar projects?
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#3Is 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.
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#4Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#5Is 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.
For what does OTP stand for? Would like to google it.
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#6Is 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.
For what does OTP stand for? Would like to google it.
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#7Is 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.
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#8can someone explain how persistence work in swimOS.
Some kind of distributed database running on each node ?
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#9Looks 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.
Re: SwimOS: Distributed platform for building stateful, real-time streaming apps
#10Is 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.