Book Image

Microservices with Go

By : Alexander Shuiskov
Book Image

Microservices with Go

By: Alexander Shuiskov

Overview of this book

This book covers the key benefits and common issues of microservices, helping you understand the problems microservice architecture helps to solve, the issues it usually introduces, and the ways to tackle them. You’ll start by learning about the importance of using the right principles and standards in order to achieve the key benefits of microservice architecture. The following chapters will explain why the Go programming language is one of the most popular languages for microservice development and lay down the foundations for the next chapters of the book. You’ll explore the foundational aspects of Go microservice development including service scaffolding, service discovery, data serialization, synchronous and asynchronous communication, deployment, and testing. After covering the development aspects, you’ll progress to maintenance and reliability topics. The last part focuses on more advanced topics of Go microservice development including system reliability, observability, maintainability, and scalability. In this part, you’ll dive into the best practices and examples which illustrate how to apply the key ideas to existing applications, using the services scaffolded in the previous part as examples. By the end of this book, you’ll have gained hands-on experience with everything you need to develop scalable, reliable and performant microservices using Go.
Table of Contents (19 chapters)
1
Part 1: Introduction
3
Part 2: Foundation
12
Part 3: Maintenance

Telemetry overview

In the introduction to this chapter, we mentioned that there are different types of service performance data, all of which are essential for service health monitoring and troubleshooting. These types of data are called telemetry data and include the following:

  • Logs: Messages recorded by your services that provide insights into the operations they perform or errors they encounter
  • Metrics: Performance data produced by your services, such as the number of registered users, API request error rate, or percentage of free disk space
  • Traces: Data that shows how your services perform various operations, such as API requests, which other services they call, which internal operations they perform, and how long these operations take

Telemetry data is immutable: it captures events that have already happened to the service and provides the results of various measurements, such as service API response latency. When different types of telemetry data are combined...