README.md

helidon-conference

Example for conferences

The MP and SE project were generated using helidon quickstart and then modified to live in a single pom project (e.g. dependency management and plugin management is unified in parent project).

conference-se

mvn archetype:generate -DinteractiveMode=false \
    -DarchetypeGroupId=io.helidon.archetypes \
    -DarchetypeArtifactId=helidon-quickstart-se \
    -DarchetypeVersion=1.1.1 \
    -DgroupId=io.helidon.examples \
    -DartifactId=conference-se \
    -Dpackage=io.helidon.examples.conference.se

conference-mp

mvn archetype:generate -DinteractiveMode=false \
    -DarchetypeGroupId=io.helidon.archetypes \
    -DarchetypeArtifactId=helidon-quickstart-mp \
    -DarchetypeVersion=1.1.1 \
    -DgroupId=io.helidon.examples \
    -DartifactId=conference-mp \
    -Dpackage=io.helidon.examples.conference.mp

Startup

To start SE application, just use java -jar, or run it from IDE. To start MP application, you need to provide the following system properties to correctly decrypt password from config:

-Dsecurity.config.aes.insecure-passphrase=myVerySecureMasterPasswordForConference 
-Dsecurity.config.require-encryption=false

Endpoints

Each application opens a few endpoints that return JSON messages.

conference-se

• http://localhost:8080/greet - unsecured endpoint that returns a "Hello World"
• http://localhost:8080/greet/jack - secured endpoint that requires login (e.g. jack/jackIsGreat or jill/jillToo)
• http://localhost:8080/greet/greeting - secured endpoint that requires a user in "admin" role (jack)
• http://localhost:8080/greet/ - unsecured endpoint that returns a "Hello "
• http://localhost:8080/metrics - all available metrics (has "vendor", "basic" and "application" subpaths)
• http://localhost:8080/health - all available healthchecks (a few built-in from helidon-health-checks and once custom)

conference-mp

• http://localhost:8081/greet - secured endpoint that returns "Hello "
• http://localhost:8081/greet/ - secured endpoint that returns "Hello (security: )"
• http://localhost:8081/greet/outbound/jack - identity propagation to conference-se service
• PUT to http://localhost:8081/greet/greeting - secured endpoint that requires a user in "admin" role (jack) to change the message
• http://localhost:8081/metrics - all available metrics (has "vendor", "basic" and "application" subpaths)
• http://localhost:8081/health - predefined healthchecks (can be extended by custom)

Tracing

To see traces of the calls, I use Zipkin tracer. To replicate the same behavior, simply start Zipkin docker image:

First time: docker run -d -p 9411:9411 openzipkin/zipkin

If Zipkin is already installed: docker start zipkin

This command will start "Zipkin" on default host and port. If you have Zipkin running on a different location than http://localhost:9411, you need to re-configure the application:

application.yaml:

# Listing default values 
tracing:
    service: "service-name" # Existing configuration
    protocol: "http"
    host: "localhost"
    port: 9411
    api-version: "2"
    enabled: true