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

## Advantages 

Decoupling via events was presented in the lesson on [Events](https://www.educative.io/courses/microservice-architecture-practical-implementation/events). Such an architecture achieves a high degree of decoupling.

Especially for distributed systems, asynchronous communication has a number
of decisive advantages:

* When a communication partner fails, the message is sent later when the communication partner is available again. In this manner, asynchronous communication offers **resilience**, that is, protection against the failure of parts of the system.

* The processing and delivery of a message can nearly always be **guaranteed**. The messages are stored for a long time.
 Processing is assured,
 for example, by the recipients acknowledging the message.

In this manner, **asynchronous communication solves challenges caused by distributed systems**.


# Advantages 

Decoupling via events was presented in the lesson on [Events](https://www.educative.io/courses/microservice-architecture-practical-implementation/events). Such an architecture achieves a high degree of decoupling.

Especially for distributed systems, asynchronous communication has a number
of decisive advantages:

* When a communication partner fails, the message is sent later when the communication partner is available again. In this manner, asynchronous communication offers **resilience**, that is, protection against the failure of parts of the system.

* The processing and delivery of a message can nearly always be **guaranteed**. The messages are stored for a long time.
 Processing is assured,
 for example, by the recipients acknowledging the message.

In this manner, **asynchronous communication solves challenges caused by distributed systems**.


In this lesson, we'll discuss advantages and variations to the approaches we've already discussed in this chapter.

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

Advantages & Variations

Advantages #