Explore different technologies for the implementation of microservices while highlighting their advantages and disadvantages.

Microservices Architecture

This module focuses on the various implementations of microservices. We’ll learn approaches for tech stacks that can be used to implement microservices. We’ll also discuss the pros and cons of each approach.
We’ll start by exploring some fundamental concepts for implementing microservices. Within each concept, we’ll learn about the different technologies used to implement it. The technologies include front-end integration with Edge Side Includes (ESI), asynchronous microservices with Kafka and REST feeds, synchronous microservices with the Netflix stack, and Consul, Docker, Kubernetes, and Cloud Foundry. Each technology is described and then demonstrated with real code.

Microservices 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.


# 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.

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

Conclusion

Chapter Conclusion

Summary #