Cruise to the Future: Role of Developers in the AI and Cloud Era
summary
Compares concrete data strategies for event-driven systems, showing when events should carry full payloads versus just identifiers, and where reads must hit monolithic data, domain-based data, or service-based data stores. Lays out specific event contract patterns, coupling costs (cross-service joins, consistency windows), and pragmatic techniques—CDC, materialized views, versioned contracts—to reduce coupling and stale reads, with trade-offs and operational implications developers face when choosing storage and retrieval approaches.
AI-written summary · about
chapters (6)
- 0:00Introduction and AI relevance
- 3:12History of fear and innovation
- 7:54AI displacing and creating jobs
- 13:39Massive AI investments and future
- 17:57Role of developers in AI and cloud era
- 21:53Summary and call to action
related talks
31mData Unleashed: A Developer's Perspective on Navigating the Architecture Maze
52mEvent Sourcing for the Cloud Developer
42mApplication Architectures: The shadows and highlights of Event Driven Design
29mFollowing the Data: A Deeper Look into Distributed Applications
25mPlatform Engineering for Modern Data Infrastructure
39mModern Event-driven Architecture: Adopting Data in Motion
52mSo You Want to Build An Event Driven System?
52mSo You Want to Build An Event Driven System?