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)

Wide column stores

Wide column stores, or column-oriented database systems, are storage systems that store data by columns rather than by rows. For example, consider the following simple table:

FirstName

LastName

Age

John

Smith

42

Bill

Cox

23

Jeff

Dean

35

In an RBDMS, the tuples would be stored row-wise, so the data on the disk would be stored as follows:

John,Smith,42|Bill,Cox,23|Jeff,Dean,35 

In online-transaction-processing (OLTP) applications, the I/O pattern is mostly reading and writing all of the values for entire records. As a result, row-wise storage is optimal for OLTP databases.

In a columnar database however, all of the columns are stored together. So, the tuples would be stored as follows:

John,Bill,Jeff|Smith,Cox,Dean|42,23,35 

The advantage here is that if we want to read values such as FirstName, reading one disk block reads...