Working with Microservices in Go

Working with Microservices in Go
MP4 | Video: h264, 1280×720 | Audio: AAC, 44.1 KHz, 2 Ch

Build highly available, scalable, resilient distributed applications using Go

What you’ll learn
Learn what Microservices are and when to use them
Develop loosely coupled, single purpose applications that work together
Communicate between services using JSON, Remote Procedure Calls, and gRPC
Learn how to implement service discovery using etcd
Learn how to push events to microservices using the Advanced Message Queuing Protocol (AMQP) using RabbitMQ

Requirements
A basic understanding of the Go programming language
A Macintosh, Windows, or Linux computer with a connection to the internet
Description
For a long time, web applications were usually a single application that handled everything-in other words, a monolithic application. This monolith handled user authentication, logging, sending email, and everything else. While this is still a popular (and useful) approach, today, many larger scale applications tend to break things up into microservices. Today, most large organizations are focused on building web applications using this approach, and with good reason.

Microservices, also known as the microservice architecture, are an architectural style which structures an application as a loosely coupled collection of smaller applications. The microservice architecture allows for the rapid and reliable delivery of large, complex applications. Some of the most common features for a microservice are

it is maintainable and testable;

it can deployed by itself;

it is organized around business capabilities;

it is often owned by a small team.

In this course, we’ll develop a number of small, self-contained, loosely coupled microservices that will will communicate with one another and a simple front-end application with a REST API, with RPC, over gRPC, and by sending and consuming messages using AMQP, the Advanced Message Queuing Protocol. The microservices we build will include the following functionality

An Authentication service, with a Postgres database;

A Logging service, with a MongoDB database;

A Listener service, which receives messages from RabbitMQ and acts upon them;

A Broker service, which is an optional single point of entry into the microservice cluster;

A Mail service, which takes a JSON payload, converts into a formatted email, and send it out.

We’ll also learn how to deploy our distributed application to a Docker Swarm and Kubernetes, and how to scale up and down, as necessary, and to update individual microservices with little or no downtime.

Who this course is for
Go developers who have worked with monolithic applications and who want to learn how to work with Microservices