Handling Legacy APIs with Domain Driven Design and Reactivity
summary
Claims a practical pattern to keep a backward‑compatible REST API while avoiding repeated polling and cache headaches by combining Domain‑Driven Design and simple reactivity: domain layer defines repository interfaces, infrastructure implements them and turns API update events into entities, and the application layer (Cubit/Bloc) calls down, bubbles up by invoking synchronous commands and subscribing to update streams. Demo app uses two repositories (integers and doubles) against one numbers API, uses repositories expose streams with injectable singletons and stream controllers, and the approach works in the migration phase.
AI-written summary · about
chapters (6)
- 0:00Welcome
- 3:02Legacy APIs challenges
- 8:52Traditional API integration problems
- 12:23Call down bubble up approach
- 13:49Live demo
- 26:58Summary
related talks
01h 10mTowards higher Reusability : Applying Clean Architecture to API Landscape.
45mDomain-Driven Design in Micro Frontends
27mBridging Business and Frontend: Domain-Driven Design in Modern Web Architecture.
49mDeveloping a clean architecture-inspired React application with MVVM
25mReact application as API
34mEffective Reactive Architecture
28mRequiem for APIs - The Evolution of Web Development
55mRethinking Reactive Architectures