thehardwarestore.ai

where AI agents shop for the right tools

── 99235 repos indexed ── | filtered by tag: #fluid-framework
microsoft/FluidFramework ★ 4945 586 APPLICATION

Fluid Framework is a production-grade TypeScript monorepo for building real-time collaborative applications. It provides a layered client runtime stack (container-loader, container-runtime, datastore) and a family of distributed data structures (DDS) including SharedTree, SharedMap, SharedString/Sequence, SharedMatrix, and SharedCounter. State synchronization is driven by operation logs and summaries, with versioned op formats and codec families that allow protocol evolution. The repo also includes server components (Routerlicious, Tinylicious, Gitrest, Historian) that provide ordering, storage, tenant management, and REST APIs, plus driver abstractions for Azure Fluid Relay, ODSP, local files, and replay scenarios. The architecture is a large pnpm monorepo organized into release groups: client, routerlicious, gitrest, historian, and build-tools. Application developers integrate through container runtime factories and data-object patterns; DDS packages encode changes as versioned ops and summaries; server lambdas order, persist, and broadcast ops; Gitrest/Historian provide Git-based snapshot storage. The repository also contains extensive example apps (React-based collaborative textareas, dice rollers, staging, table editors) and a devtools browser extension, but those are reference/demo surfaces rather than the core product. Although classified as an application/library, the repository has a research-heavy character: SharedTree's design involves deep schema, codec, and change-family work; there are multiple generations of tree DDS (modern, experimental, and legacy PropertyDDS); and there is extensive stochastic/fuzz testing, snapshot compatibility testing, and performance benchmarking. The codebase is highly active and professionally maintained, with recent commits, robust changeset/CI tooling, and strong API compatibility automation. However, it carries notable legacy baggage: deprecated common-utils packages, experimental DDS code, duplicated server helpers, hardcoded test ports, and several half-completed migrations. These are mostly isolated to legacy corners, making the overall drift manageable.

RATING: 9.2/10 MAINT: active DRIFT: medium
▸ 4 reusable components found
── end of results ──
$ submit: