Event-Driven UX in the Real World with Angular and Socket.io
summary
Demonstrates concrete patterns and working demos: real-time notifications, streaming support requests, record locks and field-level “soft” locks, and a chat that all update clients immediately. Uses socket.io with Angular 5.2 and rxjs, migrating from SignalR/.NET to Node. Claims event-driven UIs eliminate the Save button, simplify concurrency, and stop polling that would create a million extra requests per minute. Code streams items one at a time and broadcasts locks successfully.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 2:27Limitations of current paradigms
- 6:02Rethinking web interactions
- 12:12Socket implementation basics
- 22:14Streaming data patterns
- 33:03Record-level locking
- 36:47Field-level locking
- 41:06Future architecture and CQRS
related talks
38mBeyond REST: Using Full-Stack Signals for Real-Time Reactive UIs
47mThe Greatest Mystery is Realtime with Angular, NestJS, and websockets!
23mRxJS, Angular, and WebSockets - The Spy Life
41mModel-View-Websockets
45mReactive Frontends with RxJS and Angular
40mWorking with WebSockets in Angular apps
40mSocket to me
54mReactive Angular 2