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

The following drawing shows a frontend monolith which serves as the frontend for multiple microservices.


# Option: monolithic frontend and backend

Doing without modularization in the frontend is inconsistent. On the one hand, a backend is modularized into microservices which involves a great deal of effort.


On the other side is a monolithic frontend, which is an architecture that must be questioned. The result does not have to be a modularized frontend. It may also turn out that a monolithic frontend together with a monolithic backend also meets the requirements. Then you can save the effort for the modularization of the backend into microservices.


This can be the case, for example, if the advantage of separate deployment and further decoupling in other areas is not important after all.


The following drawing shows a frontend monolith
which serves as frontend for a monolithic backend.

# Option: modularly developed frontend

Of course, a **frontend deployed as a monolith can be developed modularly**.  Unfortunately, experience shows that modular development
often still leads to an unmaintainable, non-modular system in the end because the boundaries between the modules dissolve over time. The boundaries between modules that can be deployed separately, such as microservices, are not easy to circumvent so that modularization is secured in the long term.

Nevertheless, each microservice can, for example, be assigned a module in the frontend in order to decouple and parallelize the development. However, in that case, the frontend monolith still has to be deployed as a whole. Separate deployment is one advantage of microservices over other modularizations.

The following drawing shows a frontend monolith that is divided into modules.

In this lesson, we'll debate the pros and cons of a monolithic frontend and a modular frontend.

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

Frontend: Monolith or Modular?

Option: monolithic frontend and backend #

Option: modularly developed