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

Zuul is the **routing solution** that is part of the Netflix stack. 

Zuul is responsible for forwarding external calls to the correct microservice.


# Zuul vs. reverse proxy

The routing could also be provided by a Reverse Proxy. 

> A **Reverse Proxy** is a web server that is configured to forward incoming calls to other servers.



Zuul has a feature that a reverse proxy is lacking, **dynamic
filters**:
-  Depending on the properties of the HTTP request or external
configurations, Zuul can **forward certain calls to specific servers** or
execute logic for logging, for example.
- A developer can write **custom
code** for the routing decision.
-  The code can even be dynamically
loaded as Groovy code at runtime.

In this way, Zuul ensures **maximum
flexibility**.

- Zuul filters can also be used to implement central functionalities
such as **logging of all requests**.
- A Zuul filter can implement the
login, send information about the current user with the HTTP requests,
and thereby implement **authentication**. 

Zuul can **take over typical
functionalities of an API gateway** (see
[Benefits & Challenges](https://www.educative.io/courses/microservice-architecture-practical-implementation/benefits-challenges)).


In this lesson, we'll discuss routing with Zuul.

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

Router: Zuul

Introduction #

Zuul vs. reverse proxy #