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

Service discovery overview

In the previous chapter, we created an application consisting of three microservices. The relationship between the services is illustrated in the following diagram:

Figure 3.1 – Relationship between our microservices

As you can see, the movie service calls both the metadata and rating service for fetching the complete movie details.

But how would our services send requests? How would they know the addresses of each other?

In our example, we used pre-programmed static values for the API handlers. The settings we used were as follows:

  • Metadata service: localhost:8081
  • Rating service: localhost:8082
  • Movie service: localhost:8083

In our approach, each service would need to know the exact address of the other services it would communicate with. This approach would work until we more than one instance of each microservice. In this case, we would have multiple challenges:

  • What address should you...