Explore different technologies for the implementation of microservices while highlighting their advantages and disadvantages.

Microservices Architecture

This module focuses on the various implementations of microservices. We’ll learn approaches for tech stacks that can be used to implement microservices. We’ll also discuss the pros and cons of each approach.
We’ll start by exploring some fundamental concepts for implementing microservices. Within each concept, we’ll learn about the different technologies used to implement it. The technologies include front-end integration with Edge Side Includes (ESI), asynchronous microservices with Kafka and REST feeds, synchronous microservices with the Netflix stack, and Consul, Docker, Kubernetes, and Cloud Foundry. Each technology is described and then demonstrated with real code.

Microservices 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.

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

Conclusion

Cloud Foundry

Why Cloud Foundry?

Open source

Easy to install