Elevating Event-Driven World: A Deep Dive into AsyncAPI v3
0 likes49 views
The document discusses AsyncAPI v3, emphasizing the importance of event-driven architectures, reusability, and different communication patterns like pub/sub and request/reply. It highlights challenges and best practices in designing APIs, particularly in how operations are described for applications. The conclusion invites readers to engage with the AsyncAPI community through various social media platforms.
Elevating Event-Driven World: A Deep Dive into AsyncAPI v3
- 1. Elevating Event-Driven World: A Deep Dive into AsyncAPI v3 Łukasz Górnicki @derberq
- 2. 2 TOP 3 Pub/Sub Nightmare Reuse all the things! Request/reply pattern support
- 7. It’s no longer about how others can interact with your API
- 8. “describe the operations an application* performs”
- 11. “It's NOT RECOMMENDED to derive a receiver AsyncAPI document from a sender one or vice versa”
- 13. REUSABILITY
- 15. REQUEST/REPLY
- 18. “STATIC WAY” Heart Emotions Tracker Slack Server User Adds emoji to a message “hello”
- 19. “STATIC WAY” Heart Emotions Tracker Slack Server User Adds emoji to a message Send reaction_added payload “hello”
- 20. “STATIC WAY” Heart Emotions Tracker Slack Server User Adds emoji to a message Send reaction_added payload Send acknowledgment “hello”
- 23. “STATIC WAY” Heart Emotions Tracker Slack Server User Adds emoji to a message Send reaction_added payload Send acknowledgment “hello”