The SDK that Reacts: State Over Events

on YouTube ↗14m

" summary

Argues that high-frequency collaborative apps need a middle SDK layer, and shows a working stack: 100Ms SDK fronting a client-side live store built on top of zustand-like store and exposed via React, with selectors prefixed elect and a single exported actions object for UI/server/auto events. Implements queued batching (few hundred ms) so hundreds of state updates per second collapse into fewer renders, keeping state consistent across users and making the UI remain responsive at room scale.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and background
2. 1:53Challenges in data-intensive apps
3. 3:40Need for a decoupled SDK layer
4. 5:48Insights from Flux architecture
5. 8:14SDK implementation with Redux
6. 10:19Developer experience optimizations
7. 12:23Batching for performance
8. 13:04Recommendations and closing

" related talks

• 36mModern React and the case for Reactive State ManagementMichel Weststrate · YGLF 2019: Code Camp
• 26mReasonReact and local stateCristiano Calcagno · ReactEurope 2018
• 30mReact state management in a GraphQL eraKitze Ristovski · AgentConf 2018
• 01h 04mWhat makes React different?Jake Ginnivan · NDC Sydney 2016
• 27mReact, But For DataMichel Weststrate · ReactNext 2017
• 46mReact in All Its StatesAmélie Benoit · Devoxx France 2022
• 30mReact: Rethinking best practicesPete Hunt · JSConf EU 2013
• 31msetState demystifiedMichele Bertoli · ReactJS Day 2017