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

# 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.

Consul and Spring Boot

Introduction