4 ms·

I'm not familiar with this family of technology, so forgive the dumb question: But.. what is this? I read the landing page and browsed a couple examples and I

I'm not familiar with this family of technology, so forgive the dumb question: But.. what is this? I read the landing page and browsed a couple examples and I have no clue what I would use it for. Would it be a pile of distributed workers handling jobs? Sort of like pushing a job into a job queue and having a bunch of workers consume jobs? If that's the case, what are some reasons I might choose this Bastion model over a more traditional JobQueue <-> Worker model? Thanks to any replies. I feel I should be interested, but I'm confused :)

deleted 7y ago
[deleted]
vertexclique 7y ago
As landing page states it is a runtime supplies actor-model like concurrency. If you are familiar with Erlang. Bastion is the reflection of the Erlang runtime in Rust. Far beyond an actor system implementation. It is a complete system with full asynchronous communication. "...It supplies actor-model-like concurrency with a lightweight process implementation and utilizes all of the system resources efficiently guaranteeing of at-most-once message delivery." It might be a single process, pile of workers, a bunch of http servers dispatching requests, various middleware layers connected with asynchronous boundaries. With all these built on top of crash and fault recovery. For more information what it provides please take a look to my latest presentation at Rust Berlin: https://slides.com/vertexclique/crash-course-with-bastion#/ https://slides.com/vertexclique/crash-course-with-bastion#/