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

# Summary

The Netflix stack provides a variety of projects to build microservice
architectures. The stack solves the typical challenges of synchronous
microservices as follows:

## Service discovery
**Service discovery** is offered by Eureka. 

Eureka focuses on Java with the Java client, but also offers a REST API and libraries for other languages and can therefore be used with other languages.


## Resilience

For **resilience**, Hystrix is the de facto standard for Java and covers this area very well.


- Non-Java applications can use Hystrix
via a sidecar at most.

- There are ports of Hystrix for other languages like Go.
- Hystrix is independent of the other technologies and can
be used on its own.

## Load balancing
**Ribbon** implements client-side **load balancing**, which has many
advantages.

However, since Ribbon is a Java library, other technologies are difficult to use with Ribbon, especially in the area of load balancing. There are numerous load balancers that provide alternatives.

Ribbon relies on **Eureka** for service discovery but **can also use Consul**.

## Routing
**Routing** is solved by Zuul. Zuul's dynamic filters are very flexible, but many developers are familiar with reverse proxies based on web servers like Apache httpd or nginx. 

In this case, a reverse proxy might be the safer option. Additional features like SSL termination or request throttling may also be required, which Zuul does not offer.



[Chapter 11](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-JQREl9k0klo) shows how Apache httpd can be used with Consul to provide routing.
Zuul requires Eureka to find the microservices.

The servers in the Netflix stack are written in Java so that the servers from the Netflix stack and the microservices can be packed
into JAR files. 

Thanks to Spring Cloud, they are uniformly
configurable.

The handling of metrics and logs is identical and this uniformity can be an advantage for operation.


We'll conclude this chapter with a quick summary.

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

Chapter Conclusion

Summary #

Service discovery