Event-driven architectures are distributed, asynchronous, and scalable. The rise of real-time decision making, the on-demand economy, explosion of data, and the adoption of microservices have all driven the adoption of event driven architectures. Event-driven code is reactive by nature and significantly different from imperative programming.
In this breakout session, we'll examine building an event-driven application and tackle the most common stumbling blocks of EDA, including:
• How and where for maintaining state.
• How to handle transactions that span multiple services.
• REST or Kafka (or something else).
• Asynchronous testing.
We'll end by quickly (and easily) spinning up an event-driven application using Quarkus and Red Hat AMQ Streams (Apache Kafka).
15. CONFIDENTIAL designator
V0000000
Optional section marker or title
15
In this part of the presentation:
Deploying to OpenShift (Kubernetes Native)
Test Driven Development
Quarkus Dev Mode
Microprofile Reactive Messaging
20. CONFIDENTIAL designator
V0000000
What We Just Talked About
20
Summary:
Event Driven Architectures are Scalable and Efficient
So is OpenShift, and Kafka, and Quarkus
22. CONFIDENTIAL designator
V0000000
22
Red Hat Integration
YouTube
GOTO 2018 • 50.000 Orange Stickies Later • Alberto Brandolini
Eric Evans — Tackling Complexity in the Heart of Software
Links
https://domainlanguage.com/
Implementing Domain Driven Design
https://www.eventstorming.com/
https://dddcommunity.org/