Gain insights into real-world microservice implementation, exploring tech stacks, Kafka, Docker, Kubernetes, and more. Learn about synchronous and asynchronous integrations with hands-on coding demonstrations.

docker_ms2_v3.tar.gz

scs-esi

kafka

atom

links

netflix

consul

atom-kafka-scs-netflix-up

links-up

Microservices are one of the most important software architecture trends, but it’s one thing to define an architecture and quite another to implement it. 

This course focuses on the nitty-gritty details of real-world implementation. You’ll learn recipes for tech stacks that can be used to implement microservices, as well as the pros and cons of each. 

You’ll start by exploring some fundamental concepts for implementing microservices. Within each concept, you’ll learn about the different technologies used to implement it. The technologies include: Frontend Integration with Edge Side Includes (ESI), asynchronous microservices with Kafka and REST feeds, synchronous microservices with the Netflix stack and Consul, Docker, Kubernetes, Cloud Foundry. Each technology you learn about is described and then demonstrated with real code. 

By the end of this course, you’ll be a microservice pro. Whether you’re a software engineer or an engineering manager, this course will prove useful throughout your career.

Microservice Architecture: Practical Implementation

# Introduction

For each microservice, Apache httpd must have an entry in its configuration file. For this,
[Consul Template](https://github.com/hashicorp/consul-template) can be
used. 

In the example, the `00-default.ctmpl` file is used as a
template to create the Apache httpd configuration. It is written in
the [Consul Templating Language](https://github.com/hashicorp/consul-template#templating-language).
For each microservice, it creates an entry that distributes the load
between the instances and redirects external requests to these
instances.



# The template

The essential part is:


~~~~~~~~
{{range services}}

<Proxy balancer://{{.Name}}>
{{range service .Name}}  BalancerMember http://{{.Address}}:{{.Port}}
{{end}}
</Proxy>
  ProxyPass        /{{.Name}} balancer://{{.Name}}
  ProxyPassReverse /{{.Name}} balancer://{{.Name}}

{{end}}
~~~~~~~~



- The Consul Template API functions are enclosed in `{{` and `}}`. 
- For
each service a configuration is generated with `{{range service}}`. 
- It contains a reverse proxy that is configured with the `<Proxy>` element and the `Name` of the microservice. 
- This element contains the microservice instances as `BalancerMember` with the `Address` and `Port` of each instance for distributing the load between the microservice instances.
- The end is formed by `ProxyPass` and `ProxyPassReverse` which, likewise, belong to the reverse proxy.

In this lesson, we'll discuss Consul Templates.


Preface

Self-contained Systems

Concept: Frontend Integration

Recipe: Links and Client-side Integration

Recipe: Server-side Integration using Edge Side Includes (ESI)

Concept: Asynchronous Microservices

Recipe: Messaging and Kafka

Recipe: Asynchronous Communication with Atom and REST

Concept: Synchronous Microservices

Recipe: REST with the Netflix Stack

Recipe: REST with Consul and Apache httpd

Concept: Microservices Platforms

Recipe: Docker Containers with Kubernetes

Recipe: PaaS with Cloud Foundry

Appendix

Consul Template

Introduction #