Gain insights into real-world microservice implementation, exploring tech stacks, Kafka, Docker, Kubernetes, synchronous and asynchronous integrations, and more 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

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.



# Single page app (SPA)

A **single page app (SPA)** is usually an application written in JavaScript that runs in the browser and it often implements complex UI logic. Applications such as Google Maps or Gmail are examples of applications that are highly complex and must be very interactive. SPAs are ideal for these cases.

## Disadvantages
However, SPAs also have **disadvantages**:

* Since logic can be implemented in an SPA, in practice **business logic
often also leaks into the UI**. This makes further development difficult, because logic is now implemented on the server and the client and thus at two different points in two, usually different, programming languages.

* The **load times of an SPA can be higher than the load times of a simple website**. Not only must HTML be displayed, but the JavaScript code must be loaded and started. Loading times are very important in some areas like e-commerce, because the user behavior of customers depends on loading times.


## SCS based challenges
With SCSs, these problems are complemented by **further challenges** such as:

* An **SPA for the entire system** would mean that there is a **common UI**. This is forbidden in SCSs.

* An **SPA per SCS** is one possibility for providing each SCS with its own UI.
   -  In this case, switching from one SCS to another means
starting and loading a new SPA, which can take some time. 
    - Moreover, it is not easy to split one SCS into multiple SCSs, because the SPA also needs to be split up. However, a division can be important for the development of the system in order to adapt to the architecture.


Due to the high popularity of SPAs among developers, the contradictions between SPAs and SCSs in practice are a major reason
for difficulties in implementing SCSs.

An alternative is [ROCA](https://www.educative.io/courses/microservice-architecture-practical-implementation/resource-oriented-client-architecture-roca). It establishes rules that stand for classic web applications and are much easier to use with the SCS idea.


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

Create and Integrate Flask 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

Deploying a Web Application over Kubernetes

Appendix

Challenges

Limitation to web applications #

Single page app (SPA) #