forge-core 0.9.0

Core types and traits for the Forge framework
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

//! Cluster coordination and node management.
//!
//! Forge nodes discover each other via PostgreSQL without external service discovery.
//! Nodes register in `forge_nodes`, send heartbeats, and are marked dead if stale.
//!
//! # Node Roles
//!
//! Each node can assume one or more roles:
//!
//! | Role | Responsibility |
//! |------|----------------|
//! | Gateway | HTTP/WebSocket endpoints |
//! | Function | Query/mutation execution |
//! | Worker | Background job processing |
//! | Scheduler | Cron scheduling (singleton via advisory lock) |
//!
//! # Leader Election
//!
//! Singleton processes use PostgreSQL advisory locks. Only one node holds the
//! lock at a time. If the leader crashes, PostgreSQL releases the lock and
//! a standby node acquires it.
//!
//! # Key Types
//!
//! - [`NodeId`] - Unique node identifier (UUID)
//! - [`NodeInfo`] - Node metadata (hostname, roles, capabilities)
//! - [`NodeRole`] - Role enum (Gateway, Function, Worker, Scheduler)
//! - [`LeaderRole`] - Singleton role requiring leader election

mod node;
mod roles;
mod traits;

pub use node::{NodeId, NodeInfo, NodeStatus, ParseNodeStatusError};
pub use roles::{LeaderRole, NodeRole, ParseLeaderRoleError, ParseNodeRoleError};
pub use traits::{ClusterInfo, LeaderInfo};