A Business Leaders Guide to Event-Driven Architecture

This eBook defines EDA, highlighting the advantages and challenges, suggesting best use cases, and describing the internal structure in general terms with the goal of enabling better decision-making regarding deployment. Not only will you be able to better determine where to apply EDA, but also how.

What You Will Learn in this eBook:

Introduction
Introducing the fundamental characteristics of Event-Driven Architecture (EDA), when and where it is best applied, and how it interacts well with the processing of microservices in containers.

Chapter 1: Components of Event-Driven Architecture
The layers of this architecture are examined separately in this chapter, beginning with an exhaustive list of the various components active within, along with helpful descriptions of each.

Chapter 3: Event-Driven Architecture Topologies
See how events flow from capture through processing to triggered response or responses. This is the first step toward actual event processing.

Chapter 4: Event Processing Approaches in Event-Driven Architecture
Learn how events are assigned to the appropriate processors and accessed by the intended consumers.

Chapter 5: Advantages of Event-Driven Architecture
Discover how EDA delivers us to a world in which everything must be delivered upon demand.

Chapter 6: When to Use Event-Driven Architectures
More and more of today’s applications, especially those that facilitate communication between various devices, are best served in asynchronous fashion with components loosely coupled with others. EDA powerfully facilitates efficiencies from the systems they run on.

Chapter 7: EDA and Microservices
When using microservices in containers every component stands alone, separate, and loosely coupled from others. This is where EDA leads you into an environment of continuous improvement through continuous deployment (CI/CD).

Chapter 8: Disadvantages of Event-Driven Architecture
Anticipating when and how challenging issues may arise, and documenting guidance to respond to those issues is a problem, but the payoff is the kind of interoperability needed for tomorrow’s systems.

Chapter 9: Overcoming the Challenges of Event-Driven Architectures
Since the components involved are not all on the same systems there’s no roadmap to follow. The best hedge against this will be careful, comprehensive governance and documentation. EDA could just as easily signify Extremely Disciplined Architecture.

Chapter 10: Evolving Your System by Implementing
Implementing EDA represents far more than simply adopting a new architecture. It requires making a paradigm shift from a history of request-driven to a brand new event-driven practice. This is no mean feat. You’ll find yourself reminding yourself to think differently.

Chapter 11: Leveraging a Partner for EDA Success
Engage a team of experts who work together to help you achieve your EDA implementation. Yes, it takes a village

Published: July 16, 2020 | 56 pages

Stay In The Know

Sign up to get the latest news and updates.

Privacy Policy