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)

Relational model

The most common way of storing data is based on the notion of a relational model—an idea introduced by Dr. Edgar Codd in the early 1970s. Here, an entity is stored as a tuple (or row) of attributes (or columns). A database is simply a set of rows, all of which have the same set of columns (or schema). Tables are defined using a static data schema; relations between entities are modeled by foreign keys or relationship tables; rows from different tables can be referenced using foreign keys.

There are many ways of representing the conceptual data model presented earlier. However, not all representations are efficient for all use cases. To enable figuring out an optimal relational structure, Dr. Codd expressed a series of progressively more restrictive constraints on the structure of data. With each level of constraint/rules, the amount of redundancy in the...