Disclaimer: While I usually reword several pieces of the content I take as notes from books like this one, many other pieces are just literal texts extracted from the book(s). The authors of those literal texts extracted from the books are the only owners of such content. If you're the co/author, publisher, or, in general, a copyright owner of this book or related material and consider the content of this website (https://lealceldeiro.com/) doesn't comply with your work's copyright policy, please get in touch .

Main notes taken from the book Building Event-Driven Microservices by Adam Bellemare.

Chapter 1: Why Event-Driven Microservices

Domain: The problem space that a business occupies and provides solutions to. This encompasses everything that the business must contend with, including rules, processes, ideas, business-specific terminology, and anything related to its problem space, regardless of whether or not the business concerns itself with it. The domain exists regardless of the existence of the business.

Domain (and subdomain) model: An abstraction of the actual domain useful for business purposes. The main domain model of ana business is discernible through the products the business provides its customers, the interfaces by which customers interact with the products, and the various other processes and functions by which the business fulfills its stated goals.

By keeping loose coupling between bounded contexts, and focusing on minimizing inter-context dependencies, we allow bounded context implementations to change as necessary, without subsequently breaking many (or any) other systems.

Teams that find it too hard to access data in their organization, or find their products are scope-creeping because all the data is located in a single implementation, are likely experiencing the effects of poor data communication structures. This problem will be magnified as the organization grows, develops new products, and increasingly needs to access commonly used domain data.

Chapter 2: Event-Driven Microservice Fundamentals

Chapter 3: Communication and Data Contracts

Chapter 4: Integrating Event-Driven Architectures with Existing Systems

Chapter 5: Event-Driven Processing Basics

Chapter 6: Deterministic Stream Processing

Chapter 7: Stateful Streaming

Chapter 8: Building Workflows with Microservices

Chapter 9: Microservices Using Function-as-a-Service

Chapter 10: Basic Producer and Consumer Microservices

Chapter 11: Heavyweight Framework Microservices

Chapter 12: Lightweight Framework Microservices

Chapter 13: Integrating Event-Driven and Request-Response Microservices

Chapter 14: Supportive Tooling

Chapter 15: Testing Event-Driven Microservices

Chapter 16: Deploying Event-Driven Microservices

Chapter 17: Conclusion