Live data from Hacker News

Bastion – Highly-available distributed fault-tolerant runtime

github.com

1–10 of 45 posts

Re: Bastion – Highly-available distributed fault-tolerant runtime

#4
This looks promising, though the "No Forced Trait Implementations" seems to instead require using a strange looking msg!() macro?

https://docs.rs/bastion/0.3.4/bastion/macro.msg.html

Seems less clean to read than Riker (https://riker.rs), though that doesn't really do async well.

Re: Bastion – Highly-available distributed fault-tolerant runtime

#5
post #4

This looks promising, though the "No Forced Trait Implementations" seems to instead require using a strange looking msg!() macro? https://docs.rs/bastion/0.3.4/bastion/macro.msg.html Seems less clean to read than Riker ( https://riker.rs ), though that doesn't really do async well.

Yes, the msg!() macro is a little painful to write. I think it can be refactored into the pattern like `impl Handler`. But beyond that, it supports async/await naturally. :)

Re: Bastion – Highly-available distributed fault-tolerant runtime

#6
post #3

Very appreciate the work on bastion, which really gets the spirit of erlang actor programming with the supervisor-ing strategy! The code is clean and well documented, and I cannot believe the project is not well-known by rust communities.

BTW: They are working on Hot-Code Swap.

Re: Bastion – Highly-available distributed fault-tolerant runtime

#10
post #7

I have hard time understanding what this is. Is an alternative to docker somehow? What other framework/platform would bastion compete with?

So did it. I didn't know if it was a service or a library or if it integrates with something. Looks like it's a library for Rust. I think mentioning Rust would speed up the understanding of where this sits
Post reply on HN