One of the more impactful books I've read since I started writing code in Go a year ago. I've written code for about two decades, progressively trying to get better at "engineering" reliable and performant systems. This book stands out for the quality of material, but even more so for the quality of the code available as a companion on GitHub. We ended up bringing some of it into our production application - it's that good!

This book offers a comprehensive exploration of a variety of EDA topics, including architecture, design, patterns, testing, and planning. The author provides detailed information and presents the pros and cons of each concept, facilitating informed decision-making when designing a system. The level of detail and thorough explanations make this book an excellent resource for Go developers seeking to expand their knowledge and skill set. Overall, it is a valuable read for those interested in delving into high-quality EDA practices.

Event-driven Architecture creates the basis for effective microservices and containerization. Michael Stack, with “Event-Driven Architecture in Golang) (2022) delivers an exceptional and unapologetic look through Golang to build a tool, establish events, and run the process through dev, test, and prod for the user. The book introduces a generic app, Mallbots, which manages stores, ordering, delivery and associated functions to create events. Using a common framework provides a stable training base for the reader to examine their own techniques and explore other options. The book divides into three sections, an introduction to events, the components of event-driven architecture, and production ready. Recommend this book for any developing with microservices in general or Golang in particular. The first three chapters introduce various elements of event-driven architecture, the Mallbots app that will be built, and an event-storming option. One exceptional item that occurs throughout this text is the use of Unified Modeling Language (UML) images and clear diagrams showing exactly how events relate to each other in different applications. This use of constructs, and the coding examples, make it easy to follow along through every step. The last chapter here discusses a process called event-storming. It is a process building tool to evaluate functional needs with later elements that may be introduced in code. The second section builds through the tools to build the MallBots app. As an interesting approach, the tool starts from a monolithic approach with synchronous communication, introduces modules, then builds to create the asynchronous linkages with a conversion to microservices and containers. One common theme references choreography versus orchestration of events where in choreography, each piece knows what comes next while orchestration has each piece knowing only what they do, and where it must be delivered centrally. The section builds through developing sagas to explicitly detail how events are expected to occur and use dependency injection to find the flaws. The last element takes the developed Mallbots app into production. Stack includes how to test the software through a variety of different tools with a preference for using mocks in the event-driven scenarios. Once the software is tested, the book covers how to deploy to the cloud effectively and then adds in types for monitoring success. The use of OpenTelemetry to start is always a good approach and then options are offered to use Jaeger, Prometheus, and Grafana to build those items into usable metrics. The book does acknowledge a shortcoming in that only logs and metrics are used initially but this last section fixes that by adding detailed traces to the overall picture. There was very little in this approach that was not done extremely well. If I had to pick a shortcoming, a chapter covering some of the differences between Golang and other event-driven architectures could have added to the generic readers knowledge. I enjoyed that the writer was unapologetic about the use of Golang throughout, and I think it made the read much better overall but I still do enjoy comparisons. Overall, “Event-Driven Architecture with GoLang” was exactly as promised. The book details an end to end learning approach to building MallBots, transitioning from a monolithic approach to an event-driven solution, and delivering that model into production. The generic MallBots tool can be easily switched to a personal application to improve, and the UML diagrams provide solutions to modify to whatever one might be building. This makes an excellent reference, and I recommend including it on your shelf if you work in either micro-services or Golang.

Go is a multi-paradigm programming language. i.e. for a user to solve a problem using go, both object-oriented and functional paradigms can be used. While there are many books that help a reader understand the object-oriented paradigm of solving a problem, this book helps the reader understand the application of functional programming techniques in Go. The book starts with introducing the reader to the concept of Functional Programming. The second chapter helps the reader understand why the functions are powerful. Chapter 3 introduces the concept of Higher-Order functions. This chapter also introduces the reader to a variety of new concepts. Chapter 4 will help the reader understand how to write testable code with functions. Chapter 5 teaches the user about Immutability and how Go language helps in maintaining immutability in struct level. This chapter also explains the implications of Garbage Collection, Unit Testing, and pure Functional Programming.Chapter 6 to 8 is about using Functional programming Techniques. Chapter 6 talks about some practical implementations of Functions that leverage functional programming concepts. Chapter 7 helps the reader understand Recursion as in Functional Languages recursion takes center stage. Chapter 8 is about different methods of chaining functions in functional programming.Chapters 9 to 11 talk about Design Patterns and Functional Programming Libraries. While Chapter 9 talks about the Functional Desing Patterns, Chapter 10 teaches the reader about concurrency and how functional programming and how the same can be implemented using Go. Chapter 11 explains to the reader the different functional programming libraries that will help the reader build programs in a functional paradigm.This book expects the reader to have a basic understanding of Go and Generics in Go to understand all the topics better. Anybody who wants to understand about how to use functional programming in Go can get up and running quickly with this book. Kudos to the author Dylan Meeus for writing such a wonderful book.

This book does an excellent job of laying out the foundational information that so many people miss when designing distributed systems. You do not need to be a Golang expert or even a beginner to get value from this book. While walking readers through the process of converting an existing system to an event-driven architecture, it covers everything from strategic Domain Driven Design to effective testing patterns. It also does a great job of explaining the pros and cons of different architectures relative to the application context. I was given the opportunity to read a pre-release copy of this book to provide feedback and found it valuable enough that I purchased it as soon as it was available. I cannot recommend it enough.