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

# Introduction

The Consul integration in Spring Boot is comparable to the integration
of Eureka (see [Eureka: Service Discovery](https://www.educative.io/courses/microservice-architecture-practical-implementation/eureka-service-discovery)). 

There is a configuration file `application.properties`. Here is the relevant
section:


```dockerfile
spring.application.name=catalog
spring.cloud.consul.host=consul
spring.cloud.consul.port=8500
spring.cloud.consul.discovery.preferIpAddress=true
spring.cloud.consul.discovery.instanceId=\${spring.application.name}:
\${spring.application.instance_id:\${random.value}}
```

The section configures the following values:

* `spring.application.name` defines the name under which the
  application is registered in Consul.

* `spring.cloud.consul.host` and `spring.cloud.consul.port` determine
  at which port and on which host Consul can be accessed.

* Via `spring.cloud.consul.discovery.preferIpAddress` the services
  register with their IP address and not with the host name. This
  circumvents problems that arise because host names cannot be
  resolved in the Docker environment.

* `spring.cloud.consul.discovery.instanceId` assigns an unambiguous ID to each microservice instance for discriminating between instances for load balancing.


In this lesson, we'll discuss Consul and Spring boot.

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

Consul and Spring Boot

Introduction #