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

SCS describes an architectural approach that is more narrowly defined than microservices.  Therefore, **SCS cannot be the
approach for solving all problems**.

## Limitation to web applications

The first limitation of SCSs is that **they are web applications**. Thus, SCSs are not a solution when a web UI is not required.


However, some aspects of SCSs can still be implemented in a scenario that does not involve web applications: the clear separation of domains and the focus on asynchronous communication.

If a system is to be developed that offers only an API, an architecture can be created that provides at least some of the advantages of SCSs.



SCS describes an architectural approach that is more narrowly defined than microservices.  Therefore, **SCS cannot be the
approach for solving all problems**.

# Limitation to web applications

The first limitation of SCSs is that **they are web applications**. Thus, SCSs are not a solution when a web UI is not required.


However, some aspects of SCSs can still be implemented in a scenario that does not involve web applications: the clear separation of domains and the focus on asynchronous communication.

If a system is to be developed that offers only an API, an architecture can be created that provides at least some of the advantages of SCSs.



In this lesson, we'll look at some challenges pertaining to the use of 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

Challenges

Limitation to web applications #