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

[Varnish](https://varnish-cache.org/) is a web cache and is used as an ESI implementation in the example.

Varnish is mainly used for optimizing web servers:
1. It intercepts the HTTP
requests to web servers.
2. It then caches the
responses.
3. It forwards only those requests to the web servers that are **not** in the cache.

This improves performance.


# Licence and support

Varnish is licensed under a
[BSD license](https://github.com/varnishcache/varnish-cache/blob/master/LICENSE).
The cache is mainly developed by
[Varnish Software](https://www.varnish-software.com/), which also
provides commercial support.


# Caching with HTTP and HTTP headers

Caching data correctly is not a trivial matter. Above all, the questions are **when can content be retrieved from the cache and when does the data have to be retrieved from the web server** because the data in the cache no longer represents the current state? Varnish uses its own HTTP headers for this.

The HTTP protocol has very good support for caching
through its HTTP headers. The control over whether data is cached
rests with the web server, which informs the cache of the settings
via HTTP headers. Only the web server can decide whether a page can be
cached because that depends on the domain logic.


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

Varnish

Introduction #

Licence and support #

Caching with HTTP and HTTP headers #