erdos/node/mod.rs
1//! Data structures for executing and ERDOS application.
2//!
3//! ERDOS applications may run across one or several nodes connected via TCP,
4//! as set in the [`Configuration`](crate::Configuration).
5//! The [`new_app`](crate::new_app) helper function may be useful in scaling
6//! from one node to many via command line arguments.
7//!
8//! Currently, operators are manually scheduled to a [`Node`] via the
9//! [`OperatorConfig`](crate::dataflow::OperatorConfig). By default, they are
10//! scheduled on node 0. We are looking into more elegant solutions for
11//! scheduling operators, and hope to provide a versatile solution.
12
13// Private submodules
14#[allow(clippy::module_inception)]
15mod node;
16
17// Crate-wide visible submodules
18pub(crate) mod lattice;
19pub(crate) mod operator_event;
20pub(crate) mod worker;
21
22// Public submodules
23#[doc(hidden)]
24pub mod operator_executors;
25
26// Public exports
27pub use node::{Node, NodeHandle, NodeId};