SA
Swarnim Arun
@swarnimarun
Design Patterns for async and parallel systems with Rust
Submitted Oct 5, 2024
Preface
As Rust has matured it provides both async and parallel programming primitives for efficient concurrency, although Rust isn’t opionated about any specific kind of concurrency pattern. As a language Rust’s Concurrency Model derived from Send + Sync Marker traits provide even common design patterns and libraries with ways to help users avoid the most cumbersome of foot-guns in the form of data-races.
Proposal
“I would like to explore essential design patterns, crates and ecosystem for each side of the two concurrency patterns. Discuss technical details regarding higher level design of APIs and how each of the tools and means differ from other popular languages using a wide variety of similar patterns.”
- Explore writing executors and future aka async wrappers over simple Asynchronous OS APIs.
- State management across threads and tasks.
- Message passing with and without channels. Quick comparison between unix pipes and channels.
- Comparing Go, Elixir/BEAM and other systems languages(C++) to Rust’s concurrency model.
- Pain points with Rust’s concurrency model and crates/patterns to work around them.
Prerequisites
- basic familiarity with some concurrency primitives such as tasks or threads.
- basic rust understanding
- some knowledge about pointers and basic system’s design
Swarnim Arun
swarnimarun.com - Game Developer & Software Consultant
*Currently,
Senior Developer @ Cedana.ai
Working on optimizing cloud compute performance and efficiency
Comments
Hosted by
A community of Rust language contributors and end-users from Bangalore. We have presence on the following telegram channels https://t.me/RustIndia https://t.me/fpncr LinkedIn: https://www.linkedin.com/company/rust-india/ Twitter (not updated frequently): https://twitter.com/rustlangin
more
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}