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)

Summary

For the almost nine years since its inception, the popularity of Go keeps growing. The following Google Trends graph is another good indicator of the exponential growth in the interest of the language:

Reference: https://trends.google.com/trends/explore?date=2009-10-01%202018-07-30&q=golang&hl=en-US

In this chapter, we looked at how you can go about learning Go, building a team, and migrating applications to Go.

This is the last chapter in our study of Go. I hope you enjoyed reading, and at the very least got an alternative view of programming. As Alan Perlis said, in the dated-but-relevant Epigrams of Programming (http://pu.inf.uni-tuebingen.de/users/klaeren/epigrams.html), "A language that doesn't affect the way you think about programming is not worth knowing."