| Description |
1 online resource |
| Summary |
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 Description 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. 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 for This 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. |
| Contents |
Cover -- Title Page -- Copyright and Credits -- Dedication -- Contributors -- Table of Contents -- Preface -- Part 1: Event-Driven Fundamentals -- Chapter 1: Introduction to Event-Driven Architectures -- Technical requirements -- An exchange of facts -- Event notifications -- Event-carried state transfer -- Event sourcing -- Core components -- Wrap-up -- The MallBots application -- The pitch -- Application services -- API gateway services -- Clients -- A quick note about hexagons -- Benefits of EDA -- Resiliency -- Agility -- User experience (UX) -- Analytics and auditing |
|
Challenges of EDA -- Eventual consistency -- Dual writes -- Distributed and asynchronous workflows -- Debuggability -- Getting it right -- Summary -- Chapter 2: Supporting Patterns in Brief -- Domain-driven design -- DDD misconceptions -- So, what is it all about then? -- How is it useful for EDA? -- Domain-centric architectures -- An evolving solution -- Hexagonal architecture applied -- Testing -- A rulebook, not a guidebook -- Should you use domain-centric architectures? -- How is it useful for EDA? -- Command and Query Responsibility Segregation -- The problem being solved -- Applying CQRS |
|
When to consider CQRS -- CQRS and event sourcing -- Task-based UI -- Application architectures -- Monolithic architecture -- Microservices -- Recommendation for green field projects -- Summary -- Further reading -- Chapter 3: Design and Planning -- Technical requirements -- What are we building? -- Finding answers with EventStorming -- What is EventStorming? -- Big Picture EventStorming -- Design-level EventStorming -- Understanding the business -- Recording architectural decisions -- Summary -- Further reading -- Part 2: Components of Event-Driven Architecture -- Chapter 4: Event Foundations |
|
Technical requirements -- A tour of MallBots -- The responsibilities of the monolith -- Module code organization -- User interface -- Running the monolith -- A focus on event-driven integration and communication patterns -- Taking a closer look at module integration -- Using external data -- Commanding external components -- Types of events -- Domain events -- Event sourcing events -- Integration events -- Refactoring side effects with domain events -- What about the modules not using DDD? -- Summary -- Chapter 5: Tracking Changes with Event Sourcing -- Technical requirements |
|
What is event sourcing? -- Understanding the difference between event streaming and event sourcing -- Adding event sourcing to the monolith -- Beyond basic events -- Adding the event sourcing package -- Using just enough CQRS -- A group of stores is called a mall -- A group of products is called a catalog -- Taking note of the little things -- Connecting the domain events with the read model -- Recapping the CQRS changes -- Aggregate event stream lifetimes -- Taking periodic snapshots of the event stream -- Using snapshots -- Summary -- Chapter 6: Asynchronous Connections |
| Subject |
Computer architecture.
|
|
Real-time data processing.
|
|
Go (Computer program language)
|
|
Ordinateurs -- Architecture. |
|
Temps réel (Informatique) |
|
Go (Langage de programmation) |
|
Computer architecture |
|
Go (Computer program language) |
|
Real-time data processing |
| Other Form: |
Print version: 9781803232188 |
|
Print version: 1803238011 9781803238012 (OCoLC)1329426094 |
| ISBN |
9781803232188 (electronic bk.) |
|
1803232188 (electronic bk.) |
|
More Resources