Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Hands-On Software Architecture with Golang
  • Toc
  • feedback
Hands-On Software Architecture with Golang

Hands-On Software Architecture with Golang

By : Raiturkar
4 (12)
close
Hands-On Software Architecture with Golang

Hands-On Software Architecture with Golang

4 (12)
By: 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)
close

Dependencies

Services are rarely exists in isolation; they have dependencies, both upstream and downstream. Every server will receive requests from clients (either UI or other services ) that are counting on the service to honor the advertised contract and to live up to its SLAs. Each service also has a bunch of downstream dependencies (other services) that it depends on to get work done.

To understand the impact of dependencies on the overall system's, reliability, let's consider the Hotel Search service in the travel website we are building. Let's say we have built it to very high reliability levels (as described in the previous section) and we have an uptime requirement of four-nines (99.99% availability) to the clients. Now, the Hotel Search service depends on several other microservices, such as the Pricing Engine, Catalog Service, and Wallet, to display the...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete