Learn to implement microservices across a range of common tech stacks.

Scalability & System Design for Developers

In this module, we’ll look at some fundamental concepts for implementing microservices. Within each concept, 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, Cloud Foundry. Each technology is described and then demonstrated with real code.

Microservice Architecture: Practical Implementation

# Frontend integration

Frontend integration ([chapter 3](https://www.educative.io/courses/microservice-architecture-practical-implementation/events)) can be a good
addition to synchronous communication. 

# Asynchronous communication

Asynchronous communication (see
[chapter 6](https://www.educative.io/courses/microservice-architecture-practical-implementation/introduction-3wEPzo7AADQ)) is another alternative.

Synchronous and asynchronous communication are possibilities for microservices to communicate with each other on the logic level.


One of these options should be enough to build a microservices
system.

# Combination

 Of course, a **combination** of synchronous and asynchronous is also possible.

 The asynchronous communication with Atom and the synchronous communication with REST use the same infrastructure so that these two communication mechanisms can be used together very easily.


# Future chapters
The following chapters show concrete implementations for synchronous
communication. 

The examples all use REST for communication. Today REST is the preferred architecture for synchronous communication.


In principle, other approaches such as
[SOAP](https://www.w3.org/TR/soap/) or
[Thrift](https://thrift.apache.org/) are also conceivable.



We'll look at a few quick variations of what we've learned in this chapter now.

Variations

Frontend integration