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

## Message-oriented middleware (MOM)
This chapter shows the integration of microservices using a **message-oriented middleware (MOM)**.  A MOM sends messages and ensures that they reach the recipient. MOMs are asynchronous, meaning that they do not implement request/reply as is done with synchronous communication protocols, they only send messages.


MOMs have different characteristics such as: 
- **high reliability**
- **low latency**
- **high throughput**

MOMs also have a long history; they form the basis of numerous business-critical systems.



# Message-oriented middleware (MOM)
This chapter shows the integration of microservices using a **message-oriented middleware (MOM)**.  A MOM sends messages and ensures that they reach the recipient. MOMs are asynchronous, meaning that they do not implement request/reply as is done with synchronous communication protocols, they only send messages.


MOMs have different characteristics such as: 
- **high reliability**
- **low latency**
- **high throughput**

MOMs also have a long history; they form the basis of numerous business-critical systems.



In this lesson, we'll get a quick introduction to message-oriented middleware and a walkthrough of what the chapter holds for us.


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

Introduction

Message-oriented middleware (MOM) #