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

Kubernetes solves the challenges of synchronous microservices as follows:

* DNS offers **service discovery**. Thanks to DNS, microservices can be used transparently in any programming language. However, DNS only provides the IP address, so the port must be known. No code is required to register the services. When you start the service, a DNS record is created automatically.
* **Load balancing** is ensured by Kubernetes by distributing the
traffic for the IP address of the Kubernetes service to the individual
pods on the IP level. This is transparent for callers and for the
called microservice.

* **Routing** is covered by Kubernetes via the load balancer or node ports of the services. This is also transparent for the microservices.

* **Resilience** is offered by Kubernetes via the restarting of
containers and load balancing. 
    - In addition, a library like Hystrix can be useful for implementing timeouts or circuit breakers.
     - A proxy like [Envoy](https://github.com/lyft/envoy) can be
an alternative to Hystrix.
Envoy is also part of Istio and implements resilience for Istio.



# Summary

Kubernetes solves the challenges of synchronous microservices as follows:

* DNS offers **service discovery**. Thanks to DNS, microservices can be used transparently in any programming language. However, DNS only provides the IP address, so the port must be known. No code is required to register the services. When you start the service, a DNS record is created automatically.
* **Load balancing** is ensured by Kubernetes by distributing the
traffic for the IP address of the Kubernetes service to the individual
pods on the IP level. This is transparent for callers and for the
called microservice.

* **Routing** is covered by Kubernetes via the load balancer or node ports of the services. This is also transparent for the microservices.

* **Resilience** is offered by Kubernetes via the restarting of
containers and load balancing. 
    - In addition, a library like Hystrix can be useful for implementing timeouts or circuit breakers.
     - A proxy like [Envoy](https://github.com/lyft/envoy) can be
an alternative to Hystrix.
Envoy is also part of Istio and implements resilience for Istio.



In this lesson, we'll conclude this chapter with a quick summary of what we have learned.

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 #