How to design the perfect interactive media content planning tool using Hexa- and CQRS architectures
summary
Project replaces slow Excel workflows used by ~300 users (20 key editors) with a web planner that shifts writes from REST to an event-driven pipeline using Hexagonal Architecture, commands queued in Kafka and an async write path via CQRS, while reads remain HTTP. Frontend holds local state as Frontend as Master and uses RSocket for real-time client notifications. Results: slot creation and edits become instant in the UI, collaborative live updates appear to all subscribers, undo/redo implemented by emitting inverse events, and export to the canonical scheduling system succeeds.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:09Traditional TV programming challenges
- 8:29Excel scheduling workflow problems
- 10:42Design sprint and requirements
- 12:28Hexagonal architecture
- 16:45Synchronous operations performance
- 18:09CQRS for read-write separation
- 21:21Commands and Kafka integration
- 23:39Initial load improvements demo
- 26:52Retrospective and RSocket
- 31:08Event-driven RSocket
- 34:19Collaborative editing demo
- 36:07Undo and redo implementation
- 38:15Undo and redo features demo
- 39:15API evolution and architecture
- 40:46Future improvements
related talks
40mBuilding an Application with TDD, DDD and Hexagonal Architecture...
49m"Multi-Player" Enterprise Applications: Why and How to Build a Collaborative UX
42mCombining orchestration and choreography into a clean architecture
43mCommander: Better Distributed Applications through CQRS and Event Sourcing
01h 05mDDD, event sourcing and CQRS – theory and practice- 01h 05mDDD, event sourcing and CQRS – theory and practice
42mBuilding a reactive multi user document editor in ScalaJS
01h 25mBuilding microservices with event sourcing and CQRS