Skip to content

Netflix Conductor Expandability Evaluation

This project is part of the evaluation of a Saga pattern implementation using Netflix Conductor. The original Saga Pattern Realization With Netflix Conductor has been extended by a CustomerService in order to evaluate the expandability of an implementation using Netflix Conductor to realize the Saga pattern. The CustomerService has to authorize the customer before a hotel is being booked.

Start the Application

  1. Run ./gradlew clean build

  2. Execute docker-compose up --no-start

  3. Execute docker-compose start elasticsearch

  4. Execute docker-compose start dynomite

  5. Execute docker-compose up

  6. Requesting trip bookings is now possible. Either use curl commands, the provided TravelApplication.json insomnia file, which includes different trip booking requests, or access the Swagger UI of the different services:

Service
URL to Swagger UI
TravelService http://localhost:8090/swagger-ui.html
HotelService http://localhost:8081/swagger-ui.html
FlightService http://localhost:8082/swagger-ui.html
CustomerService http://localhost:8083/swagger-ui.html

An example for such a request:

TravelRequest
{
    "duration":
    {
        "start":"2021-12-01",
        "end":"2021-12-12"
    },
    "start":
    {
        "country":"Scotland",
        "city":"Stirling"
    },
    "destination":
    {
        "country":"Sweden",
        "city":"Stockholm"
    },
    "travellerName": "Max Mustermann",
    "boardType":"breakfast",
    "customerId":"1"
}

To simulate a Saga that fails because no hotel or no flight is available, use one of the following Strings as destination country in the trip booking request:

"Provoke hotel failure"

"Provoke flight failure"

To simulate a Saga that fails because the customer validation failed, the customerId in the trip booking request has to be smaller than 1, for example:

{
    ...
    customerId: "-1"
}

Additionally, the Conductor UI can be accessed via http://localhost:5000/ and the Swagger UI of the Conductor server via http://localhost:8080/.

The services also provide a health and an info endpoint that show some information about the system like that the DB is up and running. These endpoints can be accessed via:

Service
URL to health endpoint
URL to info endpoint
TravelService http://localhost:8090/api/travel/monitor/health http://localhost:8090/api/travel/monitor/info
HotelService http://localhost:8081/api/hotels/monitor/health http://localhost:8081/api/hotels/monitor/info
FlightService http://localhost:8082/api/flights/monitor/health http://localhost:8082/api/flights/monitor/info
CustomerService http://localhost:8083/api/customers/monitor/health http://localhost:8083/api/customers/monitor/info

If you are on Windows or Mac, you sometimes have to replace localhost with the default IP of your docker machine (use docker-machine ip default to get this default IP).

Stop the Application

To stop the application and remove the created containers, execute the following command:

docker-compose down --remove-orphans


NetflixConductor_Implementations/NetflixConductor_Expandability-Evaluation


Last update: 2022-02-15
Back to top