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

# Introduction

This chapter deals with the technical options for implementing
synchronous microservices. [Chapter 6](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-3wEPzo7AADQ) already
introduced the term "synchronous microservices".

> A microservice is **synchronous** if it makes a request to other microservices while processing requests and waits for the result.

The logic to handle a request in the microservice might not depend on the result of a request to a different microservice.


The drawing above illustrates this kind of communication. While the left microservice processes a request, it calls the right microservice and waits for the result of this call.

Synchronous and asynchronous communication according to this
definition are **independent of the communication protocol**.

# Synchronous protocols
A synchronous communication protocol means that **a request returns a result**. 

For example, a REST or HTTP GET returns a result in an HTTP status, a JSON document, or an HTML page. If a system processes a REST request, makes a REST request itself to another system, and waits
for the response, it is synchronous. Asynchronous REST systems were
discussed in [chapter 8](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-m2yWAKYG6p0).

In this lesson, we'll look at the definition of synchronous microservices and get a quick introduction to an example.

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

Definition

Introduction #