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

The database of the order microservice (see the drawing above) contains a table for the orders (`Ordertable`) and the individual items in the orders (`OrderLine`). Goods (`Item`) and customers (`Customer`) also have their own tables.



In the microservice **microservice-kafka-invoice**, the tables for
customers and items are missing. The customer data is stored as
part of `invoice`, and the item data as part of `invoiceLine` (see
the drawing above). The
data in the tables are copies of the customers' and items' data at
the time when the order was transferred to the system. 

This means that **if a customer changes their data or a product changes its price, it does not affect the previous invoices**. That is correct from a domain logic perspective. After all, a price change should not affect invoices that have already been written.


Otherwise, getting the correct price and customer information at the time of the invoice can be implemented only with a complete history of the data, which is quite complex. With the model used here, it is **also very easy to transfer discounts or special offers to the invoice**. It is necessary to send a different price for a product.


In this lesson, we'll look at the upcoming coding example from the perspective of its data model.

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

Example: Data Model

Data model for the database #