Gain insights into microservice principles, their pros and cons, Micro and Macro architecture, migration strategies, Docker's role, and technologies to effectively implement microservices.

docker_ms2_v3.tar.gz

SpringBoot

test

SpringMain

ms-1-scs-esi

SpringMain-copy

scs-esi

scs-esi-copy

scs-esi-up

Microservices are one of the most important and popular software architecture trends. This architecture forms the base for a lot of companies including: Amazon, Netflix, Spotify, and Uber. 

In this course you’ll learn microservices in depth and understand reasons for and against microservices. Beyond that, you’ll learn about Micro and Macro architecture, strategies for migrating old systems, the role of Docker in this architecture, and technologies for implementing microservices. 

After taking this course, you’ll be better equipped to implement microservices for your own use.

An Introduction to Microservice Principles and Concepts

The criteria from the [second lesson](https://www.educative.io/courses/introduction-microservice-principles-concepts/requirements) of this chapter for the implementation of microservices can serve as a basis to assess Go’s suitability as a microservices programming language.

# Communication

Go supports **REST** in the standard libraries. Libraries are also available for messaging systems such as **AMQP**, for example https://github.com/streadway/amqp. 

There is also a library for messaging with [Redis](https://github.com/go-redis/redis).

Due to the widespread use of Go, there is hardly any communication infrastructure that does not support Go.

# Operation

Go also offers many options for operation.

## Deployment
- The **deployment** in a Docker container is very easy with Docker multi stage builds, as already illustrated.
## Configuration
- Libraries like [Viper](https://github.com/spf13/viper) support the **configuration** of Go applications. This library supports formats such as **YAML** or **JSON**.
## Logs
- Go itself already offers support for **logs**. The Go microservices framework Go Kit contains additional features for [logs](https://godoc.org/github.com/go-kit/kit/log) in more complex scenarios.

## Metrics
- For **metrics**, [Go Kit](https://godoc.org/github.com/go-kit/kit) supports a plethora of tools such as Prometheus, but also **Graphite** or **InfluxDB**.


# New microservices

For a new microservice, it is enough to create the Docker build and then write the source code. 

# Resilience
Go Kit contains an implementation of resilience patterns such as [Circuit Breaker](https://godoc.org/github.com/go-kit/kit/circuitbreaker). In addition, there is a port of the [Hystrix library](https://github.com/afex/hystrix-go) for Go.


In this lesson, we'll see how Go fits for usage in the implementation of Microservices according to the criteria specified in the Requirements lesson.
Let's Begin! 

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Go for Microservices?

Communication #