Events, Event-driven Architecture and AsyncAPI, what the fork?

Events, Event Driven Architecture and Async APIs. Certainly you have heard about these expressions and wondered: What is this? What's it for? Why is it important? During this lecture I will answer these and other questions about the theme, passing through standards, characteristics, examples and APIs documentation form when worked asynchronously, and we'll also see how that all fits in with your API strategy.

Transcript

1. Events, Event-driven Architecture and AsyncAPI, what the fork?
2. Ana Borges Brazil API specialist at Sensedia @PaulaSimiqueli
3. APIs Industry Recognition Visionary by That’s all we do Organizer of API Experience One of the largest API-focused event in the world 1 100 Enterprise customers + Presence in LatAm and Europe CONSULTING SERVICES API PLATFORM Strong Performer and Leader by ABOUT SENSEDIA Best Current Offering API Strategy & Delivery Services 2019
4. “By 2020, event-sourced, real-time situational awareness will be a required characteristic for 80% of digital business solutions, and 80% of new business ecosystems will require support for event processing.” Top 10 Strategic Technology Trends for 2018
5. EVENT DRIVEN ARCHITECTURE
6. 1 EVENTS • Event: Every action that generates change of state. • Business Event: …. It is an event that has meaning for the company's activities. Order from a customer Bank Payment Product Change PRODUCTION DETECTION REACTION
7. 1 EVENT-DRIVEN ARCHITECTURE Event Consumer(s) MEDIATOR OR BROKER Event generator(s) TOPOLOGY
8. 1 EVENT-DRIVEN ARCHITECTURE TOPOLOGY MEDIATOR Event Processors EVENT MEDIATOR Events Events Queue EVENT CHANNEL
9. 1 EVENT-DRIVEN ARCHITECTURE TOPOLOGY MEDIATOR Customer Service Address Change Event Mediator Notification Service Quotation Service Queue
10. 1 EVENT-DRIVEN ARCHITECTURE TOPOLOGY BROKER Event Processors EVENT BROKER Events
11. 1 EVENT-DRIVEN ARCHITECTURE TOPOLOGY BROKER Customer Service Address Change Notification Sevice Quotation Service Quotation Queue Notification Queue
12. 1 EVENT-DRIVEN ARCHITECTURE PRINCIPLES • It reports current events • It sends notifications • It responds immediately • Communication flows only in one direction • It is command-free
13. 1 EVENT-DRIVEN ARCHITECTURE • Event Notification; • Event Carried State Transfer; • Event Sourcing. STANDARDS
14. 1 EVENT-DRIVEN ARCHITECTURE STANDARDS EVENT NOTIFICATION Customer Service Address Change Database Event Broker Offers Service Banking service “Customer X changed data” GET /customers/X • Uncoupling from receiver to sender • Producer requisition overload. PROS CONS
15. 1 EVENT-DRIVEN ARCHITECTURE STANDARDS EVENT CARRIED STATE TRANSFER Customer Service Address Change Database Event Broker Offers Service Banking service “Customer X updated the zip code to “123” • Resilience • Reducing the Producer requisition overload. Database Database PROS • Information replication • Data Consistency CONS
16. 1 EVENT-DRIVEN ARCHITECTURE STANDARDS EVENT SOURCING Database Event: Address Change PROS CONS Customer Service Address Change Event Data Source • Audit • Debug • Not very familiar. • Event Schema “Customer X updated the zip code to “123”
17. 1 ASYNCAPI • It is a specification. • Focus on the application and the channels it uses to communicate. • Event payload definition, channel name, application / transport headers and protocol DOCUMENTATION
18. 1 ASYNCAPI DOCUMENTATION
19. 1 ASYNCAPI DOCUMENTAÇÃO
20. 1 ASYNCAPI DOCUMENTAÇÃO
21. 1 EVENT-DRIVEN ARCHITECTURE PROS CONS • Coupling Reduction • Asynchronous operations • Easy to add new consumers • Highly scalable and distributed. . • May lead to loss of information • It can add more complexity if poorly implemented. • Challenge for data and flow governance. PROS/ CONS
22. 1 ...AND NOW? 1. Understand your need 2. Choose the best architecture 3. Choose the pattern 4. Choose the tool that best meets your need 5. Hands-on
23. 1 EVENTS HUB Subscriber EVENTS HUB Native APPs Cloud APPs Partner APPs Publisher • PUSH for subscribers • Automatic message retry for subscriber • Safety
24. sensedia.com Obrigada! Contacts: ana.borges@sensedia.com @PaulaSimiqueli ➔ Download - poster (A2) API DESIGN REFERENCE GUIDE http:/ /sensedia.com/apidays