diff --git a/assets/books/data/books.yaml b/assets/books/data/books.yaml
index b679e87..fa5101e 100644
--- a/assets/books/data/books.yaml
+++ b/assets/books/data/books.yaml
@@ -113,6 +113,24 @@
     - hard
     - read
     - top
+- title: Building Event-Driven Microservices
+  subtitle: Building Event-Driven Microservices
+  cover: building-event-driven-microservices.jpeg
+  order: 1
+  weight: 1
+  draft: false
+  url: https://www.oreilly.com/library/view/building-event-driven-microservices/9781492057888/
+  authors:
+    - Adam Bellemare
+  release: 2020
+  pages: 321
+  desc: |-
+    TODO
+  learning_paths:
+    - event-driven-architecture
+  badges:
+    - intermediate
+    - scheduled
 - title: Building an Event-Driven Data Mesh
   subtitle: Patterns for Designing & Building Event-Driven Architectures
   cover: building-an-event-driven-data-mesh.jpeg
@@ -125,11 +143,13 @@
   release: 2023
   pages: 275
   desc: |-
-    TODO
+    The process of building an Event-driven architecture is no easy feat, the first step to doing it well is communicate with the stakeholders of the different bussiness domains involved, hear their needs, and identify the different communication patterns, entities and events in an event storming session. There are also crucials thing like ensuring the quality of the information served from the sources, the cataloging system of the information served, and stablishing an easy and secure way for interested clients to access those sources. All this and more is explained in detail in what could be seen as a complement of the [Building Event-Driven Microservices](https://www.oreilly.com/library/view/building-event-driven-microservices/9781492057888/) book content.
   learning_paths:
     - event-driven-architecture
   badges:
-    - TODO
+    - hard
+    - read
+    - nice
 - title: Designing Distributed Systems
   subtitle: Patterns and Paradigms for Scalable, Reliable Services
   cover: designing-distributed-systems.jpeg
@@ -260,23 +280,6 @@
     - event-driven-architecture
   badges:
     - TODO
-- title: Building Event-Driven Microservices
-  subtitle: Building Event-Driven Microservices
-  cover: building-event-driven-microservices.jpeg
-  order: 1
-  weight: 1
-  draft: false
-  url: https://www.oreilly.com/library/view/building-event-driven-microservices/9781492057888/
-  authors:
-    - Adam Bellemare
-  release: 2020
-  pages: 321
-  desc: |-
-    TODO
-  learning_paths:
-    - event-driven-architecture
-  badges:
-    - TODO
 - title: Enterprise Integration Patterns
   subtitle: Designing, Building, and Deploying Messaging Solutions
   cover: enterprise-integration-patterns.jpeg
diff --git a/assets/learning-paths/data/learning-paths.yaml b/assets/learning-paths/data/learning-paths.yaml
index a6d072e..be75ac4 100644
--- a/assets/learning-paths/data/learning-paths.yaml
+++ b/assets/learning-paths/data/learning-paths.yaml
@@ -201,16 +201,17 @@
   tags: ["grpc", "http", "graphql", "websocket", "api-gateway", "rate-limit", "quotas", "openapi", "contract-testing"]
 - name: Event Driven Architecture (EDA)
   ref: event-driven-architecture
-  status: coming-soon
+  status: in-progress
   desc: |
-    Coming soon
+    Different from typical inter-service communication patterns like REST APIs or gRPC, event driven architectures allow to increase flexibility, agility, and speed in development processes by decoupling services. Synchronous calls are replaced by publishing events into a broker, from which the interested clients can receive the information. But there are many challenges when building this kind of architecture: re-adjusting the way teams think about communications, ensuring the information integrity and quality produced by the sources, stablishing secure and painless ways for consumers to integrate with the data sources, and more. Luckily the industry has evolved and experience in EDA is being documented in book and articles to let anyone learn good practices and how to overcome the many challenges ahead!.
   summary: |
-    Asynchronous communication between services is possible using events. There is a lot to learn here, the main challenge is changing the way you think about information distribution.
+    Asynchronous communication between services is possible using events. There is a lot to learn here, the main challenge is changing the way you think about communication patterns.
   suggested:
     - system-design
     - microservices
     - apis
     - serverless
+  tags: ["lously-coupled", "flexibility", "nats", "kafka", "pulsar", "json-schema", "avro", "event-storming", "event-sourcing", "schema-registry"]
 - name: Serverless
   ref: serverless
   status: coming-soon