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

# Frontend integration

Frontend integration ([chapter 3](https://www.educative.io/courses/microservice-architecture-practical-implementation/events)) can be a good
addition to synchronous communication. 

# Asynchronous communication

Asynchronous communication (see
[chapter 6](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-3wEPzo7AADQ)) is another alternative.

Synchronous and asynchronous communication are possibilities for microservices to communicate with each other on the logic level.


One of these options should be enough to build a microservices
system.

# Combination

 Of course, a **combination** of synchronous and asynchronous is also possible.

 The asynchronous communication with Atom and the synchronous communication with REST use the same infrastructure so that these two communication mechanisms can be used together very easily.


# Future chapters
The following chapters show concrete implementations for synchronous
communication. 

The examples all use REST for communication. Today REST is the preferred architecture for synchronous communication.


In principle, other approaches such as
[SOAP](https://www.w3.org/TR/soap/) or
[Thrift](https://thrift.apache.org/) are also conceivable.



We'll look at a few quick variations of what we've learned in this chapter now.

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

Variations

Frontend integration #

Asynchronous communication