Gain insights into real-world microservice implementation, exploring tech stacks, Kafka, Docker, Kubernetes, synchronous and asynchronous integrations, and more 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 

In general, **integration at the frontend level should always be considered when possible**. Too often, microservices are implemented only as an approach to the backend, although by focusing on the frontend, the coupling can be looser, and the system can be simpler and more flexible. It can also be ensured that the entire logic, including the logic for the UI, is actually implemented in the microservice.

Frontend integration **allows loose coupling of microservices**. Already the use of links and of some JavaScript code can be enough to integrate the frontends of different microservices. It is therefore important not to immediately define a complex technology stack, but to first find out what can be achieved by simple means. 

This leads to another advantage: **technical complexity** of the solution is **not particularly high**; only web applications are used. There are more of them than usual, but there are no new technologies.

But even when using server-side integration, the integration in the frontend is still not particularly complex and still leads to a loose
coupling.


Here's a quick conclusion of the chapter.

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

Create and Integrate Flask 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

Deploying a Web Application over Kubernetes

Appendix

Chapter Conclusion

Summary #