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

## Variations
This chapter refers to the PaaS concept. Cloud Foundry is not the only
available PaaS.

* [OpenShift](https://www.openshift.com/) supplements Kubernetes with support for different programming languages to automate the generation of the Docker containers.


* [Amazon Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/)
  is only available on the Amazon Cloud. It can install applications in virtual machines and scale these virtual machines. Elastic Beanstalk represents a simplification compared to the IaaS approach. Since Beanstalk is based on IaaS and some additional features, Beanstalk rests on a very stable foundation. In Beanstalk applications, additional services from the Amazon offer can be used. These include databases and MOMs. Elastic Beanstalk benefits from the numerous components available in the Amazon Cloud.

* [Heroku](https://www.heroku.com/) is only available in the public
cloud. Similar to Cloud Foundry it has buildpacks for supporting
different programming languages and a marketplace for additional
services.

# Variations
This chapter refers to the PaaS concept. Cloud Foundry is not the only
available PaaS.

* [OpenShift](https://www.openshift.com/) supplements Kubernetes with support for different programming languages to automate the generation of the Docker containers.


* [Amazon Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/)
  is only available on the Amazon Cloud. It can install applications in virtual machines and scale these virtual machines. Elastic Beanstalk represents a simplification compared to the IaaS approach. Since Beanstalk is based on IaaS and some additional features, Beanstalk rests on a very stable foundation. In Beanstalk applications, additional services from the Amazon offer can be used. These include databases and MOMs. Elastic Beanstalk benefits from the numerous components available in the Amazon Cloud.

* [Heroku](https://www.heroku.com/) is only available in the public
cloud. Similar to Cloud Foundry it has buildpacks for supporting
different programming languages and a marketplace for additional
services.

In this lesson, we'll look at some variations and experiments that can be conducted with Cloud Foundry.

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

Variations & Experiments

Variations #