Book Image

Cloud Native programming with Golang

By : Mina Andrawos, Martin Helmich
Book Image

Cloud Native programming with Golang

By: Mina Andrawos, Martin Helmich

Overview of this book

Awarded as one of the best books of all time by BookAuthority, Cloud Native Programming with Golang will take you on a journey into the world of microservices and cloud computing with the help of Go. Cloud computing and microservices are two very important concepts in modern software architecture. They represent key skills that ambitious software engineers need to acquire in order to design and build software applications capable of performing and scaling. Go is a modern cross-platform programming language that is very powerful yet simple; it is an excellent choice for microservices and cloud applications. Go is gaining more and more popularity, and becoming a very attractive skill. This book starts by covering the software architectural patterns of cloud applications, as well as practical concepts regarding how to scale, distribute, and deploy those applications. You will also learn how to build a JavaScript-based front-end for your application, using TypeScript and React. From there, we dive into commercial cloud offerings by covering AWS. Finally, we conclude our book by providing some overviews of other concepts and technologies that you can explore, to move from where the book leaves off.
Table of Contents (19 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
7
AWS I – Fundamentals, AWS SDK for Go, and EC2

Microservices design patterns


In this section, we will discuss some important design patterns and architectural approaches that can help us build robust and effective cloud-ready microservices. Let's get started.

Sacrificial architecture

Sacrificial architecture is an important design approach that doesn't typically get the attention it deserves. It was mentioned by Martin Folwer in 2014 and can be found at https://martinfowler.com/bliki/SacrificialArchitecture.html.

The core idea of sacrificial architecture is that we should write our software in a way where it is easily replaceable in the future. To understand the previous statement better, let's consider an example scenario. Let's say that a couple of years ago, we had built a computer networking application that utilizes custom data serialization formats designed by our developers. Today, we need to rewrite the application in a more modern programming language that can handle a lot more data load and user requests. This task will not be...