Event-Driven Architecture in Golang

Begin building event-driven microservices, including patterns to handle data consistency and resiliency Key Features Explore the benefits and tradeoffs of event-driven architectures with practical examples and use cases Understand synergy with event sourcing, CQRS, and domain-driven development in software architecture Build an end-to-end robust application architecture by the end of the book Book DescriptionEvent-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. Youll 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. Youll then build an application made of several microservices that communicates using both choreographed and orchestrated messaging. By the end of this book, youll be able to build and deploy your own event-driven microservices using asynchronous communication.What you will learn Understand different event-driven patterns and best practices Plan and design your software architecture with ease Track changes and updates effectively using event sourcing Test and deploy your sample software application with ease Monitor and improve the performance of your software architecture Who this book is forThis hands-on book is for intermediate-level software architects, or senior software engineers working with Golang and interested in building asynchronous microservices using event sourcing, CQRS, and DDD. Intermediate-level knowledge of the Go syntax and concurrency features is necessary.