From Integration to Interaction... Holistic (Re)creation of Applications
summary
Discusses building robust integration middleware to avoid fragile point‑to‑point connections by using queuing/backfill and identifier mapping when systems use different keys. Recommends deciding sync frequency (real‑time vs nightly), prototyping user flows, freezing core requirements early, and emphasises communication, automated retries and testing integration paths before rollout.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:51Business requirements
- 8:08System architecture mess
- 13:05Why integration matters
- 19:28Poor communication pitfalls
- 25:08Project perspective
- 31:16Common sense vs logic
- 33:52Summary & Q&A
related talks
44mThinking Asynchronously: App Integration Patterns for Microservices
49m"Multi-Player" Enterprise Applications: Why and How to Build a Collaborative UX
49mJust in Time Architecture
56mBalancing Coupling in Software Design
41mRefactoring your legacy applications the right way
44mHighly Available, Distributed & Resilient Software... Team
59mEffective Microservice Communication and Conversation Patterns
51mRedesigning a Complex Web Application - Best Practices & Learnings