Event-First Thinking: Building Data-Driven Integration Architectures
summary
Argues that event-driven integration replaces brittle point-to-point plumbing in huge SAP landscapes by standardizing event metadata and routing; SAP builds a developer portal called Business Accelerator Hub and publishes about 650 events externally, uses AsyncAPI and CloudEvents for machine‑readable contracts, and runs multiple brokers (AMQP for proprietary flows) with monitoring, classification (notification vs data), and cataloging. Claims the approach scales to banks and telcos and prevents data loss when implemented.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 1:12Limitations of point-to-point integration
- 3:43Event-Driven Architecture benefits
- 5:30Event sources and brokers overview
- 7:12Standardizing event metadata
- 9:01Master data distribution use case
- 11:28Transitioning to event-first integration
- 13:18Monitoring and tracking events
- 15:27Categorizing event types
- 16:52AsyncAPI and CloudEvents specifications
- 18:18Event catalog and developer portal
- 19:42Internal vs external event catalogs
- 21:10Data integration and AI readiness
- 23:18Key takeaways and conclusion
- 23:39Q&A session
related talks
12mPlatform-First SAP Integration
25mEnterprise App Integration: A Data-Driven Approach
39mModern Event-driven Architecture: Adopting Data in Motion
17mOvercome By Events - Apache Kafka And Event-oriented Architecture
45mReliable Integration Architecture with EventStoreDB
40mThe Changing Face Of ETL: Event-driven Architectures for Data Engineers
30mModern ERP as the Platform Backbone
45mArchitecture and Tools for Selected Data Integration Cases (Part 1)