the heart of everything Three main pillars in our data strategy Our central data distribution platform High-level overview of DIAL Why Streaming? High-level overview of our Streaming platform Confluent Kafka Streaming Platform Technology overview Key challenges & platform evolution What challenges did we run into, and how did we tackle those? Streaming brings value to AAB But how is value being created in practice? 6-9-2024 | 2
6-9-2024 | 6 Data Distribution Data Marketplace Digital Integration & Access Layer (DIAL) Data Provider Data Consumer Data sharing agreement Data delivery Define datasets Search & request access B. Rapid Access to Authorised Data C. Accelerate Data Driven Decisions A. Making fit for purpose data
Processing Streaming Data Hardware Most storage and processing resources requirement to process large batches of data. Less storage required to process current data packets. More processing resources required to “stay awake” in order to meet real-time processing guarantees Performance Latency could be minutes, hours, or days Latency must be guaranteed in milliseconds Dataset Large batches of data Continuous streams of data Analysis Complex computation and analysis of a larger time frame Simple reporting or computation
Producers Overview of the current implemented connection types CDC Sink connector for files Sink connector for Database Kafka Client Kafka Client Use cases in Production Use cases in lower environments (DTA) Kafka Replicator
JMS Kafka connectors Replicator JDBC source/sink Cloud storage Hadoop / SFTP MQ and other brokers Cloud other Schema registry Monitoring Kafka REST API’s Kafka provides various api’s to manage the platform. Producer and Consumer API’s are available Azure Monitor is used for OS, Platform Logs & JMX monitoring kSQLDB and Kafka Streams Build applications and microservices using Kafka Streams and ksqlDB Schema Registry provides a serving layer (RESTful interface) for your metadata. For storing and retrieving your Avro, JSON and Protobuf schemas. New New New
partition for global ordering ✓ Use transactional producer/consumer for exactly once semantics ✓ Use Idempotent consumer to handle duplicates 6-9-2024 | 16 One type of governance doesn’t fit all usecases Make the right data for a specific purpose discoverable by consumers Loosely-coupling mindset in a strictly regulated environment Integration with the existing landscape Smooth transition from sharing events locally towards sharing enterprise- wide