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)

Monitoring

Once your code is deployed, you need to monitor what's going on. This requires upfront investment in figuring out the monitoring architecture and setting things up so that you are not blind once the application goes live. Without monitoring, when there are inevitable outages, your team will have limited insight into what's going on. This will hamper debuggability and ultimately impact the customer experience.

This is why proper monitoring is essential. There are five aspects to monitoring:

  • Proper logging
  • Proper emission of all relevant and important metrics from the application and infrastructure
  • Well-designed dashboards that reflect the health of the application
  • Actionable alerting system on the key metrics measured
  • Having a production reliability team, which might include a Site Reliability Engineering (SRE) team and an efficient on-call rotation schedule...