Event-Driven Architectures and Messaging Systems
Use event-driven architecture with Clojure and NoSQL when asynchronous boundaries improve scalability or resilience.
This section bridges the chapter overview and the detailed lessons below. For Java engineers, the practical question is how to handle event-driven systems with Clojure and NoSQL in Clojure code at the database boundary.
| Review focus |
What to check |
| Events |
Make event contracts explicit and versionable. |
| Delivery |
Design for duplicate, delayed, or failed messages. |
| State |
Know how events update NoSQL projections or read models. |
Use the child lessons to move from concept to implementation. The section goal is to make the trade-off visible before the code hardens around a database assumption.
In this section
-
Event-Driven Architecture (EDA): Core Concepts, Advantages, and Use Cases
Explore the fundamentals of Event-Driven Architecture (EDA), its advantages, and practical use cases in building scalable, responsive, and decoupled systems using Clojure and NoSQL.
-
Implementing Event-Driven Architecture (EDA) with Clojure
Explore how to implement Event-Driven Architecture using Clojure, leveraging messaging systems like Apache Kafka and RabbitMQ, and Clojure libraries such as Jackdaw and Langolier.
-
Designing Event Streams with NoSQL: A Comprehensive Guide for Java Developers
Explore the intricacies of designing event streams using NoSQL databases, focusing on append-only logs, schema evolution, replayability, and eventual consistency management.
Revised on Saturday, May 23, 2026