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

# Definition

A **self-contained system (SCS)** is a type
of microservice that **specifies elements of a macro architecture**. SCSs do not represent a complete macro architecture. The area of operation, for instance, is completely missing.

The idea behind SCS is to provide microservices that are self-contained, providing everything needed for the implementation of a part of the domain logic.


This means an SCS includes **logic,
data, and a UI**. That also means if a change impacts all technical layers, it can still be contained in one SCS, making it easier to perform the change and put it into production. 

So, an SCS for a microservice **payment** would store all information relevant to payment -- that is, it would implement a **bounded context**. But it would **also implement the UI** -- web pages to show the payment history or make a payment. **Data** about customers or ordered items would need to be replicated from other SCSs.



In this lesson, we'll look at a quick introduction to self-contained systems.

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

Definition #