Using Async API schema to define event driven architecture with AWS SNS

on YouTube ↗22m

" summary

Built an ingestion service that validates events, attaches attributes and publishes to AWS SNS topics, letting consumers create their own SQS queues or HTTP subscriptions and own filter policies so routing work disappears. Uses AsyncAPI schema as contract so producers and consumers develop in parallel with a single source of truth. Relies on AWS SNS topic filtering for boolean attribute matching and fan‑out to multiple consumers. Deployed pipeline removes a custom router, reduces maintenance, and works in production for multiple Postman teams to publish and subscribe independently.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 1:35What is Event-Driven Architecture?
3. 3:42Benefits of Event-Driven Architecture?
4. 6:18What is SNS (Simple Notification Service) ?
5. 7:44How does the message filtering work on SNS?
6. 10:53How attribute based message filtering works at SNS
7. 13:04Use case at Integrations Squad in Postman
8. 17:00How Async API helped us
9. 17:56What if-teams don't use Async API
10. 18:29Servers
11. 19:37Security
12. 20:23Channel & Schemas

" related talks

• 13mTurbocharging your Developer EcosystemPooja Thakrani, Abhishek Sivakumar · AACoT 2023 Bangalore
• 57mManaging Asynchronous APIsIan Cooper · NDC Oslo 2021
• 44mUnlocking Business Agility with Event-Driven ArchitecturesOskar Neumann, Dirk Fröhner · AWS Summit Berlin 2023
• 38mEvent-driven ArchitectureDanilo Poccia · AWS Summit Online EMEA 2020
• 20mAPI Management for Event-Driven MicroservicesFran Méndez · apidays Helsinki 2019
• 22mAsync API Specification 2.0Franz Mendez · apidays Barcelona 2019
• 21mUsing the AsyncAPI Ecosystem for your Event-Driven ArchitectureHugo Guerrero · AsyncAPI Conf 2022
• 44mThinking Asynchronously: App Integration Patterns for MicroservicesRebekah Kulidzan · GOTO EDA Day 2022