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)

GraphQL

The REST API paradigm is very elegant, and it is easy to model most real-world use cases with little difficulty. However, for the modern fast-paced web development needs, the rigid server-defined endpoints and schema can be a drag on developer productivity. Also, as discussed previously, the standard is not really network-efficient, especially if the client needs just a subset of the resource attributes. For example, let's say we are developing a mobile app, that has a search results page. Here, we don't want to get all the attributes of the hotels, since we may not have the screen real estate (or usability) to show all the data. To engineer this with a REST API, one needs to have a set URL and schema that gives all the hotels. However, if the app is deployed on a "tab", we may want to show slightly more information than on an app form factor. We can...