Book Image

Event-Driven Architecture in Golang

By : Michael Stack
5 (1)
Book Image

Event-Driven Architecture in Golang

5 (1)
By: Michael Stack

Overview of this book

Event-driven architecture in Golang is an approach used to develop applications that shares state changes asynchronously, internally, and externally using messages. EDA applications are better suited at handling situations that need to scale up quickly and the chances of individual component failures are less likely to bring your system crashing down. This is why EDA is a great thing to learn and this book is designed to get you started with the help of step-by-step explanations of essential concepts, practical examples, and more. You’ll begin building event-driven microservices, including patterns to handle data consistency and resiliency. Not only will you learn the patterns behind event-driven microservices but also how to communicate using asynchronous messaging with event streams. You’ll then build an application made of several microservices that communicates using both choreographed and orchestrated messaging. By the end of this book, you’ll be able to build and deploy your own event-driven microservices using asynchronous communication.
Table of Contents (18 chapters)
Part 1: Event-Driven Fundamentals
Part 2: Components of Event-Driven Architecture
Part 3: Production Ready

Design and Planning

It is now time to put into practice what we talked about in the previous two chapters. As the saying goes, before we can run, we must learn to walk, and before we can walk, we must learn to crawl. We were introduced to the MallBots application back in Chapter 1, Introduction to Event-Driven Architectures, but before we can create that application, we must have a plan built on a better understanding of the problem the application is intending to solve.

In this chapter, we will cover the following topics:

  • What are we building?
  • Finding answers with EventStorming
  • Understanding the business
  • Recording architectural decisions

We will be using Domain-Driven Design (DDD) discovery and strategic patterns as the basis for our initial approach. To facilitate the discovery, a workshop technique called EventStorming will be used to organize meetings with domain experts and developers. The knowledge we gain from these meetings about our application...