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
For synchronous microservices, Cloud Foundry's solutions are very
similar to those of Kubernetes.

* **Service discovery** also works via DNS making it transparent for client and server. In addition, no code needs to be written for the registration.

* **Load balancing** is also transparently implemented by Cloud Foundry.
If several instances of a microservice are deployed, the requests are
automatically
distributed to these instances.

* For the **routing** of external requests, Cloud Foundry relies on DNS
and a distribution of the requests to the various microservice instances.

* For **resilience**, the Cloud Foundry example uses the Hystrix
library. Cloud Foundry itself does not offer a solution in this area.

In addition, a PaaS provides a standardized runtime environment for microservices and can be an important antidote to the high
level of operational complexity that microservices bring. Thus, a **PaaS
enforces a standardization** that is often desirable in the context of
macro architecture.

Compared to Docker or Kubernetes
([chapter 13](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-myLVqzPNWnR)), a **PaaS provides less flexibility**. This
can also be a strength due to the standardization that goes hand in
hand with reduced flexibility.

 Modern PaaS also offers the possibility of **adapting the environment** with concepts like buildpacks or running Docker containers with arbitrary applications.


# Benefits

* PaaS solves typical problems of microservices like load balancing, routing, and service discovery.

* Cloud Foundry introduces no code dependencies.

* PaaS cover operation and deployment.

* PaaS enforce standardization and are thereby the definition of a macro architecture.

* Developers only have to deliver applications. Docker is hidden.

# Challenges

* Cloud Foundry requires a complete switch of the operation approach.

* Cloud Foundry is powerful, but also complex.

* Cloud Foundry provides a high degree of flexibility, however,
  compared to Docker containers this flexibility still has its limits.

We'll end 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 #