Tag:architecture
All the posts with the tag "architecture".
The lazily Architecture: One Reactive Graph from Local Memory to the Network
A full-architecture tour of lazily — the reactive core (Context, Cell, Slot, Signal, Effect), the three execution contexts (single-threaded, thread-safe, async), the Snapshot/Delta wire protocol that carries the same graph state across IPC, WebSocket, WebRTC, and FFI, and the cross-language family. With use cases and diagrams.
Slot → Cell → Signal: Composing Lazy and Eager Reactivity in One Graph
How lazily-rs composes three primitives — Cell, Slot, and Signal — so you can pick lazy (compute-on-read) or eager (recompute-on-change, no unset window) per derived value inside a single dependency graph. With use cases and diagrams.
Reactive State Machines: How lazily-rs Drives agent-doc's Cycle State
A finite state machine shouldn't be a pile of scattered if-checks. This post shows how lazily-rs's StateMachine primitive — a Cell-backed FSM with a pure transition function and reactive observers — became the single transition authority for agent-doc's per-document cycle state, replacing ad-hoc phase guards with one declared table. With diagrams of the phase graph, the FSM-plus-durable-journal architecture, and how the same reactive graph that runs your UI can run your protocol.
Lazily: Reactive Primitives Done Right — Context, Slots, Cells, and Signals
Introducing lazily — a multi-language reactive primitives library (Rust, Zig, Python) built on lazy invalidation. Deep dive into Context, Slot, Cell, and Signal abstractions, lazy vs eager reactivity, and how proper hydration (code and body) eliminates waste.