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
Eureka implements service discovery as we learned in the [introduction](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-YVgRzwVEQy2).

For synchronous communication, microservices have to find out at **which port and IP address other microservices can be accessed**.



# Features
Let's discuss some essential characteristics of Eureka.

## REST interface

Eureka has a **REST interface**.

Microservices can use this interface
to **register or request information** about other microservices.

## Replication

Eureka supports **replication**. 

The information from the Eureka servers is distributed to other servers  enabling the system to **compensate for the failure** of Eureka servers. 

In a distributed system, service discovery is essential for communication between microservices. Therefore, service discovery must be implemented in a way that a **failure of one server does not cause the entire service discovery to fail**.

## Cache improved performance

Due to **caches on the client**:
- The performance of Eureka **very
good**. 
- **Availability is improved** because the information is stored on the client compensating for server failure.
- The server only sends information to the client about new or deleted microservices and not information about all registered services, **communication very efficient**.

## Amazon Web Services support

Netflix supports **AWS (Amazon Web Services)**, i.e., the Amazon Cloud.


In AWS, servers run in **availability zones**. These are basically
separate data centers. The failure of an availability zone does not
affect other availability zones.

Several availability zones form a **region** which is located in a geographical zone. For example, the data centers for the region called EU-West-1 are located in Ireland.

Eureka can take regions and availability zones into account and offer a microservice instance from the same availability zone to a client as a result of the service discovery in order to increase speed.

## Crash detection

Eureka expects the microservices to regularly send **heartbeats**. 

In
this way, Eureka detects crashed instances and excludes them from the
system. This increases the probability that Eureka will return service instances that are available.

However, it may happen that a microservice instance is returned even though it is no longer running.

But whether a microservice instance has crashed or not is obvious once it is used so that a different instance can be used if it has crashed.



In this lesson, we'll discuss service discovery with Eureka.

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

Eureka: Service Discovery

Introduction #

Features #

REST interface #

Replication #

Cache improved performance #