2018 (codeone) type safe approach to invoking restful services with microprofile rest client

@CesarHgt @ivanjunckes @tomitribe
César Hernández, Ivan Junckes Filho
Type-Safe Approach to Invoking RESTful
Services with MicroProfile Rest Client

SPEAKERS
César Hernández
● Senior Software Engineer at Tomitribe
● Java Champion
● Duke’s Choice Award 2016, 2017
● Oracle Certified Professional
● +10 experience with Java EE
● Eclipse Committer: Jakarta EE TCK,
JAX-WS and Microprofile.
● Open Source advocate, teacher and
public speaker
Ivan Junckes
● Software Engineer at Tomitribe
● Oracle Certified Professional
● 9+ years experience with JavaEE
● Eclipse Committer: JnoSQL, JPA, JSONB
and JSP
● Member of GujavaSC

Slides and resources

Eclipse MicroProfile
● An open-source community specification
● Focus on Enterprise Java microservices
● Generates: SPEC, API, and TCK.
● https://microprofile.io
● Implemented by different vendors.

Eclipse MicroProfile
MicroProfile 2.1
JAX-RS 2.1JSON-P 1.1CDI 2.0
Config 1.3
Fault
Tolerance 1.1
JWT
Propagation
1.1
Health
Check 1.0
Metrics 1.1
Open
Tracing 1.2
Open API
1.0
= Updated
= No change from last release (MicroProfile 2.0)
Rest Client
1.1
JSON-B 1.0
Rest Client
1.1
Open
Tracing 1.2

So far...

RESTful client API’s so far in Java
● JAX-RS
○ Jersey
○ Apache CXF
○ RestEasy
● Others client implementations
○ Apache HttpComponents
○ Spring
○ Unirest
○ java.net.HttpURLConnection ?
https://jersey.github.io/documentation/latest/client.html
http://cxf.apache.org/docs/jax-rs-client-api.html
http://hc.apache.org/

htps://blogs.oracle.com/theaquarium/java-ee-8-community-survey-results-and-next-steps
Why we have
so many
options?

● Java 8
● Maven 3.9
● Apache TomEE 8.0.0-M1
● Rest Client for MicroProfile 1.1
● Inget 1.0
Demo architecture

Tests included on
movie-app/services module.
○ Jersey
○ Apache CXF
○ Apache HttpComponents
movie-app/services/MoviesResource.java
/GET movies
/GET movies/{id}
/GET movies/count
/POST movies
/PUT movies/{id}

MicroProfile Rest Client
● Type safe approach based on interfaces
● Implicit transformation
● Uses JAX-RS 2.0 APIs
● Lastest version: 1.1
○ Asynchronous Methods
○ RestClientBuilderListener
○ Supports java.net.URI in addition to java.net.URL.
○ @RegisterRestClient is now a bean-defining annotation
● https://microprofile.io/project/eclipse/microprofile-rest-client

helloWorld.mp.restClient();

pom.xml
<dependency>
<groupId>org.apache.tomee</groupId>
<artifactId>javaee-api</artifactId>
<version>8.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.eclipse.microprofile</groupId>
<artifactId>microprofile</artifactId>
<version>1.3</version>
<type>pom</type>
<scope>provided</scope>
</dependency>

More problems...
● Copy / pasting everything would be very boring
● Easy to make mistakes
● Microservices evolve too fast
● Maintaining a client would be a nightmare
● Cost is too high

@radcortez @ivanjunckes @tomitribe
Inget

Inget
● Open source project
● Model (Amazon-style)
● Resource
● Client
● Command-line Interface (CLI)
● Documentation

Evolving the demo architecture
movie-app
cinema-desktop-app
cinema-webapp
client
client client
Generates

Evolving the demo architecture

movie-app/client/pom.xml
<dependency>
<groupId>org.tomitribe.inget</groupId>
<artifactId>inget-client-java</artifactId>
<version>${version.inget}</version>
</dependency>

movie-app/client/pom.xml<plugin>
<groupId>org.tomitribe.inget</groupId>
<artifactId>inget-maven-plugin</artifactId>
<version>${version.inget}</version>
<configuration>
<modelPackage>org.superbiz.moviefun.model</modelPackage>
<resourcePackage>org.superbiz.moviefun.rest</resourcePackage>
<resourceSuffix>Resource</resourceSuffix>
<generateClient>true</generateClient>
<clientName>MovieClient</clientName>
</configuration>
<executions>
<execution>
<id>gen</id>
<phase>generate-sources</phase>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
</plugin>

What’s next in version 1.2?
● Enhancement
○ Header and cookies propagation (JWT header)
○ Make interface type available to providers
○ CDI Interceptor support
○ Non generated config keys for @RegisterRESTClient
○ Spec clarifications
● Future:
○ JAX-RS 2.1
https://github.com/eclipse/microprofile-rest-client/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aenhancement

Thank you

2018 (codeone) type safe approach to invoking restful services with microprofile rest client

Recommended

More Related Content

What's hot (20)

Similar to 2018 (codeone) type safe approach to invoking restful services with microprofile rest client (20)

More from César Hernández (20)

Recently uploaded (20)

2018 (codeone) type safe approach to invoking restful services with microprofile rest client