The Future of Messaging? Store-Carry-Forward Protocols
summary
Argues that store-carry-forward Delay/Disruption Tolerant Networks (DTNs) — opportunistic phone relays, cooperative train gateways, vehicular meshes — map to AsyncAPI's model and tooling, enabling protocol-agnostic descriptions and design-first workflows. Claims the current spec supports proof-of-concept use (publish/subscribe, channels, reusable components) and that missing behavior (carrier-as-broker, carbon scheduling) fits into bindings and extensions. Leaves open whether the spec needs core additions for large-scale DTN production and for standardized carbon-aware signaling.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:29Delay/Disruption Tolerant Networks
- 6:21Store-Forward
- 10:33Relay Strategies
- 13:43Use Cases
- 30:33Fit of AsyncAPI with DTN
- 32:34Specification
- 36:19Publishing and subscribing
- 38:26Reusing components
related talks
57mManaging Asynchronous APIs
22mAsync API Specification 2.0
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
02mBringing Clarity to Complex Event Driven Architectures with Standardized API Language
01h 03mOpenAPI and AsyncAPI, when to use which and why
31mAsyncAPI is here to stay
21mRequest-Reply Messaging Patterns: Real-World Use Cases with AsyncAPI 3.0
27mAsyncAPI & The future of API specs