Awesome

IBM Cloud Architecture - Microservices Reference Application for Netflix OSS

Netflix OSS on Bluemix - Zuul Edge Proxy

Description

This project contains a packaged Zuul Proxy edge proxy server for use in a Netflix OSS-based microservices architecture. This enables individual microservices to dynamically proxy & route communications between external and internal components. The repository builds the Zuul component into a runnable JAR that can either be used directly in Cloud Foundry or built into a Docker image (with the Dockerfile provided).

This repository, and its parent reference application, are built to enable deployment and learning of building and operating microservices-based applications on the IBM Cloud, but due to the OSS-based nature of the components involved, this reference application can be deployed to any cloud or on-premises environment as desired.

Parent Reference Application

This project is part of the IBM Cloud Architecture - Microservices Reference Application for Netflix OSS suite.

For full reference application overviews and deployment guidance, please refer to the root repository above. The overall project consists of multiple sub projects:

Standard Netflix OSS-based microservice architecture components, like Eureka and Zuul
Sample Spring Boot applications which provide a REST API and communication between each other.
Deployment pipeline and automation guidance

The Microservices Reference Application for Netflix OSS is maintained by the IBM Cloud Lab Services and Cloud Solution Engineering teams.

Application Architecture

IBM Cloud Architecture - Microservices Reference Application for Netflix OSS
The Microservices Reference Application for Netflix OSS leverages Zuul as its main edge proxy mechanism, controlling all inbound traffic into the application. You can see where Eureka is used, highlighted in the diagram below.
IBM Cloud Architecture - Cloud Native Microservices Reference Application for OmniChannel
The Zuul Proxy component is also leveraged in the OmniChannel Application as its main proxy interface between external and internal microservices. You can see where Zuul is used, highlighted in the diagram below.

APIs in this application:

There are no explicit APIs exposed by Zuul. It is meant to be an API Gateway to the other APIs in your application.

Pre-requisites:

Install Java JDK 1.8 and ensure it is available in your PATH
(Optional) HS-256 Shared Secret Key. This shared secret key is a Base-64 URL encoded string used by IBM API Connect to sign JWT Tokens. The Zuul proxy uses the JWT token signature to verify that the API caller is IBM API Connect and rejects all other callers with an HTTP 401 Unauthorized response. This is implemented as a Zuul "pre" filter. The shared secret must match what is entered into IBM API Connect definitions. A sample key has been provided in the git projects, but a new one can be generated following the steps outlined here. To update the key, open the application yaml file in src/main/resources/application.yml and replace the sharedSecret (i.e. VOKJrRJ4UuKbioNd6nIHXCpYkHhxw6-0Im-AupSk9ATvUwF8wwWzLWKQZOMbke-xxx) with the value generated in the "k" property in the JSON object:
```
security:
  sharedSecret: VOKJrRJ4UuKbioNd6nIHXCpYkHhxw6-0Im-AupSk9ATvUwF8wwWzLWKQZOMbke-xxx
```
(Optional) A local Docker instance (either native or docker-machine based) running on localhost to host container(s). Click for instructions.
(Optional) Apache Maven is used for an alternate build system. Click for instructions.

Build the Application Component

Build the application. A utility script is provided to easily build using either Gradle (default) or Maven. You can optionally specify the -d parameter to build the associated Docker image as well. The default Gradle build instructions use a Gradle wrapper requiring no further installation. The Maven build instructions require Maven to be installed locally.

1.1 Build the application using Gradle:
```
./build-microservice.sh [-d]
```
1.1 Build the application using Maven:
```
./build-microservice.sh -m [-d]
```

Run the Application Component Locally

You will need a local Eureka application instance running to connect to, from which Zuul will proxy requests to additional service instances.
You can now run either the JAR file or the Docker image locally.

1.1. To run the JAR file locally, you can simply pass parameters to the Java command in the command prompt:
java -jar docker/app.jar
1.2. To run the Docker file locally, you can pass the same paramters to start the local Docker image:
docker run -p 8080:8080 netflix-zuul:latest
Verify there is a Zuul Proxy service visible in your Eureka Dashboard at http://localhost:8761/.

Run the Application Component on Bluemix

You will need a Eureka application instance running to connect to, from which Zuul will proxy requests to additional service instances. The instance of Eureka must be accessible to the Zuul containers from public Bluemix. Make note of this fully-qualified URL. (eg http://netflix-eureka-cloudarch.mybluemix.net/eureka/)
Edit the Bluemix Response File to select your desired external public route, application domain, and other operational details. The default values in the .bluemixrc are acceptable to deploy in to the US-South Bluemix region.
To deploy Zuul as a container group onto the Bluemix Container Service, execute the following script and pass in the previously-noted Eureka location:
bluemix/deploy-container-group.sh http://netflix-eureka-cloudarch.mybluemix.net/eureka/

This script will create a clustered group of homogeneous containers, with additional management capabilities provided by Bluemix. The parameter passed into the script is the location of the Eureka service discovery container group, so that the Zuul Proxy container group can register with it upon startup.
The script will complete rather quickly, but the creation of the necessary Container Group and clustered containers may take a few moments. To check on the status of your Zuul Container Group, you can run the following command:
cf ic group ls | grep zuul_cluster

Once you see a value for Status of CREATE_COMPLETED, your Zuul Proxy instance will now be publicly accessible through the URL configured in the Bluemix response file.

Validate the Application Component Deployment

Validate that the Eureka user interface appears after a few seconds of the application being started.
Verify that there is a registered zuul-proxy microservice registered with Eureka, visible in the Eureka Dashboard.
You can now run additional services that register with Eureka and contact them through the Zuul Proxy. For instance, a service registered as weather-service in Eureka is accessible through the following Zuul Proxy URL:
3.1. Locally: http://localhost:8080/weather-service/ (with localhost:8080 being the default location of the running Zuul Proxy instance)
3.2. Bluemix: http://netflix-zuul-cloudarch.mybluemix.net/weather-service (with netflix-zuul-cloudarch being your configured PROXY_HOSTNAME in the .bluemixrc file)