OutcomeWhat did you decide?
Due dateWhen does this decision need to be made by?


To support a various number of use cases Iroha2 must implement logic to plug additional logic as an actor. The design should allow an arbitrary actor to receive messages from other actors and share messages about his work.


The current runtime design is implemented using mpsc. The single receiver channel architecture turns into a chaos of strict dependencies and creates constraints for extending logic with new modules.


Rework core architecture with actor model and single message bus. Bus receives all messages during execution of actors and broadcast them to others. Message trait should allow identify nature of message to filter it. To prevent any blocking problems, messages must reference an immutable value or a cloned value.

According to the requirement of supporting different use cases, actors should be implemented as compile-time features (at least) or as pluggable extensions (point to discuss and future research).


List all decisions you and other stakeholders made


  1. Use available actor frameworks such as Actix or different


  1. Tradeoff between extensibility and overhead with maintenance global bus and filter messages


  1. Filtering messages on message bus layer against skipping on actors
  2. Research pros and cons of actors as separate binaries with external API to extend pluggability


List all risks in form "description \[probability (from 0 to 9); impact (from 0 to 9)\]"

Additional Information
Simple implementation of a lock-free, bounded, single-producer, multi-consumer, broadcast channel
Popular actor framework for Rust
Type-safe & high-perf distributed actor systems with Rust by Eickhoff, Anselm