Book Image

Hands-On Software Architecture with Golang

By : Jyotiswarup Raiturkar
Book Image

Hands-On Software Architecture with Golang

By: Jyotiswarup Raiturkar

Overview of this book

Building software requires careful planning and architectural considerations; Golang was developed with a fresh perspective on building next-generation applications on the cloud with distributed and concurrent computing concerns. Hands-On Software Architecture with Golang starts with a brief introduction to architectural elements, Go, and a case study to demonstrate architectural principles. You'll then move on to look at code-level aspects such as modularity, class design, and constructs specific to Golang and implementation of design patterns. As you make your way through the chapters, you'll explore the core objectives of architecture such as effectively managing complexity, scalability, and reliability of software systems. You'll also work through creating distributed systems and their communication before moving on to modeling and scaling of data. In the concluding chapters, you'll learn to deploy architectures and plan the migration of applications from other languages. By the end of this book, you will have gained insight into various design and architectural patterns, which will enable you to create robust, scalable architecture using Golang.
Table of Contents (14 chapters)

Integration patterns

The messaging primitives we just looked at can be augmented with various functionalities to enable complex architectural patterns. In Chapter 5, Going Distributed, we took a look at the event-driven architecture paradigm. In this this section, we will have a more detailed look at various patterns of integrating components with messaging.

While these patterns can be implemented, in principle, through durable messaging (Kafka, NSQ, and so on), we will use use Golang channel primitives to demonstrate integration patterns.

The request-reply pattern

In this pattern, Service-A (requestor) wants some work from from Service-B (responder), and there is output expected out of the request. How does Service-B respond...