Skip to content

N31: Actor pattern server #969

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.

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

Merged
Merged
Changes from 1 commit
Commits
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
11 changes: 11 additions & 0 deletions content/news/031/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,17 @@ _Discussions: [Twitter][bevy_minesweeper_twitter], [dev.to][Bevy Minesweeper]_
[@ManevilleF]: https://github.com/ManevilleF
[bevy_minesweeper_twitter]: https://twitter.com/ManevilleF/status/1495787155280510977?s=20&t=omNFCI2cWgDFNC0MC7NWTg

### [Actor Pattern with Async Rust]

@Sorokya ([twitter][sorokya-twitter], [github][sorokya-github]) [published a blog
post][Actor Pattern with Async Rust] about how they improved their game server
by switching over to an actor pattern approach. This method allowed the server
to be refactored to be more modular and cleaner.

[Actor Pattern with Async Rust]: https://eo-rs.dev/blog/the-actor-pattern-with-async-rust/
[sorokya-twitter]: https://twitter.com/sorokya
[sorokya-github]: https://github.com/sorokya

## Tooling Updates

### [Vismut]
Expand Down