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

## Why Cloud Foundry?
[Cloud Foundry](https://www.cloudfoundry.org/) serves as PaaS technology for the example in this course. The following are the reasons for this:

### Open source
Cloud Foundry is an **open source project** involving a number of
companies. 

Cloud Foundry is managed by a **foundation**, in which Cloud Foundry providers such as **Pivotal, SAP, IBM, and Swisscom** are organized.


This ensures broad support in addition to the already many PaaS based on the Cloud Foundry.


### Easy to install
Cloud Foundry can be easily installed as a Pivotal Cloud Foundry for
Local Development on a *laptop* to set up a local PaaS for developers
to test microservices systems.

### Common
 There are many public cloud providers who have an offering based on
Cloud Foundry. An overview can be found at:
  <https://www.cloudfoundry.org/how-to-try-cloud-foundry/>.

### Can be installed on your own data center
 Finally, Cloud Foundry can be installed in your own data center.
[Pivotal Cloud Foundry](https://pivotal.io/platform) is, for example, an option for this.



# Why Cloud Foundry?
[Cloud Foundry](https://www.cloudfoundry.org/) serves as PaaS technology for the example in this course. The following are the reasons for this:

## Open source
Cloud Foundry is an **open source project** involving a number of
companies. 

Cloud Foundry is managed by a **foundation**, in which Cloud Foundry providers such as **Pivotal, SAP, IBM, and Swisscom** are organized.


This ensures broad support in addition to the already many PaaS based on the Cloud Foundry.


## Easy to install
Cloud Foundry can be easily installed as a Pivotal Cloud Foundry for
Local Development on a *laptop* to set up a local PaaS for developers
to test microservices systems.

## Common
 There are many public cloud providers who have an offering based on
Cloud Foundry. An overview can be found at:
  <https://www.cloudfoundry.org/how-to-try-cloud-foundry/>.

## Can be installed on your own data center
 Finally, Cloud Foundry can be installed in your own data center.
[Pivotal Cloud Foundry](https://pivotal.io/platform) is, for example, an option for this.



In this chapter, we'll gain a quick introduction to the PaaS technology, 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

Cloud Foundry

Why Cloud Foundry?

Open source

Easy to install

Common

Can be installed on your own data center