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
Microservices platforms appear to be very helpful due to the
large number of features, even though the operation of these platforms
can be complex. 

In practice, **Kubernetes** is a very important platform for the operation of microservices, while **PaaS such as Cloud Foundry** are not as useful, despite their seemingly useful features.

Microservices platforms should be considered for microservices because they represent **a significant simplification and complete solution** to typical microservices challenges. 

The only reason
**against** a microservices platform is the **high cost of installation**. In
the case of a small number of microservices or at the beginning of a project, the installation of a microservices platform can be bypassed. In addition, this effort is eliminated if a public cloud offer is
used.


# Summary
Microservices platforms appear to be very helpful due to the
large number of features, even though the operation of these platforms
can be complex. 

In practice, **Kubernetes** is a very important platform for the operation of microservices, while **PaaS such as Cloud Foundry** are not as useful, despite their seemingly useful features.

Microservices platforms should be considered for microservices because they represent **a significant simplification and complete solution** to typical microservices challenges. 

The only reason
**against** a microservices platform is the **high cost of installation**. In
the case of a small number of microservices or at the beginning of a project, the installation of a microservices platform can be bypassed. In addition, this effort is eliminated if a public cloud offer is
used.


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 #