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

# Summary
- ESIs are a possible implementation of frontend integration and lead to **loose coupling**. The applications are simple web applications that, apart from the ESI tag, have no dependencies on the infrastructure.

- The integration with ESIs has the advantage that the **web pages are completely assembled by the cache and can be displayed directly in the browser**. 
Therefore, the page isn't delivered unusable in any way due to fragments that still have to be loaded.

- Using a cache together with ESI has the advantage that **fragments can be cached**. 
    - This means that static pages and static parts of dynamic pages can be cached, which improves performance.
    - The pages can even be cached and 
assembled from a CDN that supports ESI, further improving performance.

- The cache can also be used to achieve a certain degree of **resilience**.
   - If a web server fails, the cache can return the old data. In this way, the web page remains available but could potentially return invalid information. 
   - However, the cache must hold the pages a long time in order for this to happen.
   - In addition,
the cache must also check the availability of the services.

## Benefits

* Web page is always delivered in entirety 
* Resilience via cache
* Higher performance via cache
* No code in the browser

## Challenges

* Uniform look and feel
* Additional server infrastructure necessary

In this lesson, we'll look at a quick summary of what we've learned 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

Chapter Conclusion

Summary #