Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

README: fix some typos #173

Merged
merged 1 commit into from
Feb 24, 2020
Merged

README: fix some typos #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,17 +100,17 @@ You can use this to launch automatically supervised tasks.
* Kill your application in certain condition or restart you subprocesses whenever a certain condition is met.

## Guarantees
Copy link
Contributor Author

@enkore enkore Feb 24, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the items under this heading don't seem like guarantees to me, e.g. "completely asynchronous system design" is more of a feature that might imply certain guarantees. "Asynchronous program boundaries" also seems entirely like a feature to me, ditto for "dynamic supervision ..."

Copy link
Contributor

@o0Ignition0o o0Ignition0o Feb 24, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's very true, maybe we can open a followup issue to discuss it ?

edit: opened a followup issue :)

* At most once delivery for all the messages.
* At most once delivery for all messages.
* Completely asynchronous system design.
* Asynchronous program boundaries with [fort](https://github.com/bastion-rs/fort).
* Dynamic supervision of supervisors (adding a subtree later during the execution)
* Lifecycle management both at `futures` and [lightproc](https://github.com/bastion-rs/bastion/tree/master/lightproc) layers.
* Faster middleware development.
* Above all "fault-tolerance".
* Fault tolerance above all.

## Why Bastion?
If one of the questions below answered with yes, then Bastion is just for you:
* Do I need fault-tolerancy in my project?
If you answer any of the questions below with yes, then Bastion is just for you:
* Do I need fault-tolerance in my project?
* Do I hate to implement weird Actor traits?
* I shouldn't need a webserver to run an actor system, right?
* Do I want to make my existing code unbreakable?
Expand Down