jbcnconf 2017: Emergency Dispatcher Demo

Emergency Dispatcher Demo for JBCN Conf 2017

Goals and Motivations

This repository contains a simple example using the following frameworks:

• Spring Cloud Data Flow
• Spring Cloud Bus
• Spring Boot
• Eureka (and Feign)
• Activiti Process Engine

This example is intended to show how we can improve communication and collaboration with Domain Experts that can express their Domain Knowledge using different types of Models. These microservices show how we can mix and match the tools that we have available, to make sure that we use the best tool for the job at hand.

Services

• Patient Record Service: just a Patient Repository
• Emergency Source: Endpoint in charge of receiving Emergency Notifications, it will dispatch the notification using the message bus, so it can be processed asap.
• Emergency Enricher: Processor in charge of decorating the initial emergency report with more information. This Processor uses other services such as the Patient Record Service to decorate the emergency information with extra data if the Patient is known by the organization. This service process the emergency and send via a message the decorated Emergency.
• Emergency Dispatcher: This service is in charge of deciding how to deal with a specific Emergency. This service will have the domain expertise to know which of the available procedures should be used to deal with an Emergency based on the Emergency available information.
• Emergency Procedure : these services represent different types of procedures for different types of emergencies.
• Procedure Registry: this service encapsulate an instance of Eureka that is used to register each of our procedures and their metadata
• Gateway: this service will automatically discover other services and expose them via http in the port 8080

Set up and Run

We are using Spring Data Flow to connect Sources, Processors and Sinks together via Streams We are also using Docker compose in order to start some providers such as RabbitMQ

Build all Maven modules (@TODO: create script):

Run 'mvn clean install' in all the maven modules

Start Docker Compose Rabbit MQ And Zipkin Docker Compose

cd docker/ docker-compose up -d

cd .. cd zipkin/ docker-compose up -d

Download Spring Data Flow

curl -O http://repo.spring.io/snapshot/org/springframework/cloud/spring-cloud-dataflow-server-local/1.2.2.BUILD-SNAPSHOT/spring-cloud-dataflow-server-local-1.2.2.BUILD-20170601.204606-1.jar java -jar spring-cloud-dataflow-server-local-1.2.2.BUILD-20170601.204606-1.jar

Start the Server

java -jar spring-cloud-dataflow-server-local-1.2.1.RELEASE.jar

Download and start the Data flow shell (in a new terminal tab)

curl -O http://repo.spring.io/snapshot/org/springframework/cloud/spring-cloud-dataflow-shell/1.2.2.BUILD-SNAPSHOT/spring-cloud-dataflow-shell-1.2.2.BUILD-20170601.204606-1.jar java -jar spring-cloud-dataflow-shell-1.2.2.BUILD-20170601.204606-1.jar

Flo -> UI

If the Data Flow server is started you can access to the UI by pointing the Browser to: http://localhost:9393/dashboad

Registering Apps and configuring & deploying the stream definition

app register --name emergency-source --type source --uri maven://com.example:emergency-source:jar:0.0.1-SNAPSHOT

app register --name emergency-enricher --type processor --uri maven://com.example:emergency-enricher:jar:0.0.1-SNAPSHOT

app register --name emergency-dispatcher --type sink --uri maven://com.example:emergency-dispatcher:jar:0.0.1-SNAPSHOT

stream create --name emergency-stream --definition ‘emergency-source | emergency-enricher | emergency-dispatcher’

stream deploy --name emergency-stream

Starting other required services

The stream will automatically bootstrap and register the Emergency Source, Emergency Enricher and Emergency Dispatcher projects, but you still need to boot up the following indepentendent modules:

• Gateway: cd gateway/ mvn spring-boot:run
• Procedure Registry Service: cd procedure-registry-service/ mvn spring-boot:run
• Patient Record Service: cd patient-records-service/ mvn spring-boot:run
• Emergency Procedure Default: cd emergency-procedure-default/ mvn spring-boot:run
• Emergency Procedure X: (you can start as many as you want of these procedures) cd emergency-procedure-(xx)/ mvn spring-boot:run

Creating a New Emergency Request

The Emergency Source project expose a REST endpoint where you can send new Emergencies. These emergencies will be propagated to the Emergency Enricher which will decorate the emergency information by calling the Patient Record Service using RestTemplate. Once the Emergency is decorated it will send a message that will be picked up by the Emergency Dispatcher which will query Eureka to see which Procedures are available and based on the information inside the Emergency it will dispatch the Emergency to one of these procedures instances.

In order to create a new emergency you need to send a POST request to http://localhost:8080/emergency-source/api/emergency/ With the following body:

{ "ssn": "ABC-123", "location": { "latitude": 1, "longitude": 2 }, "date": 1496648974639, "code": "011" }

Alternatively, you can use the Chrome (extension) POSTman collection that you can found in root directory.

To access Eureka Service registry you can go to http://localhost:9393/dashboard To access Zuul (Gateway) routes you can go to: http://localhost:8080/routes To access Zipkin (Tracer) UI you can go to: http://localhost: