v4

Contents

    MicroProfile 4.0 is based on Jakarta EE 8, the first MicroProfile release to be based on Jakarta EE (replacing the role of Java EE). Although Jakarta EE 8 is API backwards compatible with Java EE 8, Jakarta EE replaces Java EE dependencies with Jakarta EE dependencies for all MicroProfile specifications.
    MicroProfile 4.0 ships with incompatible changes to five of the APIs, namely Config, Fault Tolerance, Health, Metrics and OpenAPI.

    What's New in MicroProfile 4.0

    v4.0 18/12/2020
    01 Spec aligned with Jakarta EE 8
    02 Based on Java SE 8
    03 Jakarta CDI v2.0
    04 Jakarta JAX-RS v2.1
    05 Jakarta JSON-B v1.0
    06 Jakarta JSON-P v1.1
    07 Jakarta Annotations v1.3
    08 Eclipse MicroProfile Config v2.0
    09 Eclipse MicroProfile Fault Tolerance v3.0
    10 Eclipse MicroProfile Health v3.0
    11 Eclipse MicroProfile JWT Authentication v1.2
    12 Eclipse MicroProfile Metrics v3.0
    13 Eclipse MicroProfile Open API v2.0
    14 Eclipse MicroProfile Open tracing v2.0
    15 Eclipse MicroProfile Rest Client v2.0

    Eclipse MicroProfile Config

    GitHub repository
    Configuration de l'app en dehors de l'app.

    Rationale
    The majority of applications need to be configured based on a running environment. It must be possible to modify configuration data from outside an application so that the application itself does not need to be repackaged.
    The configuration data can come from different locations and in different formats (e.g. system properties, system environment variables, .properties, .xml, datasource). We call these config locations ConfigSources. If the same property is defined in multiple ConfigSources, we apply a policy to specify which one of the values will effectively be used.
    Under some circumstances, some data sources may change dynamically. The changed values should be fed into the client without the need for restarting the application. This requirement is particularly important for microservices running in a cloud environment. The MicroProfile Config approach allows to pick up configured values immediately after they got changed.

    Releases

    Key points 

    @Inject
@ConfigProperty(name = "foo.bar.url")
private String url;

    Eclipse MicroProfile Fault Tolerance

    GitHub repository

    Rationale
    Currently there are at least two libraries to provide fault tolerance. It is best to uniform the technologies and define a standard so that micro service applications can adopt and the implementation of fault tolerance can be provided by the containers if possible.

    Releases

    With Istio - https://istio.io
    Attention aux interactions entre annotations ! Certanines modifient le comportement d'autres !!!

    → https://github.com/NottyCode/fault-tolerence-examples

    Eclipse MicroProfile Health

    GitHub repository

    Rationale
    Health checks are used to probe the state of a computing node from another machine (i.e. kubernetes service controller) with the primary target being cloud infrastructure environments where automated processes maintain the state of computing nodes.
    In this scenario, health checks are used to determine if a computing node needs to be discarded (terminated, shutdown) and eventually replaced by another (healthy) instance.
    It’s not intended (although could be used) as a monitoring solution for human operators.

    Releases

    Key point 

    @Health
public class FooBar implements HealthCheck {}

    Eclipse MicroProfile JWT Authentication

    GitHub repository

    Rationale
    Eclipse MicroProfile JWT Authentication provides role based access control (RBAC) microservice endpoints using OpenID Connect (OIDC) and JSON Web Tokens (JWT).

    Releases

    @Claim

    Eclipse MicroProfile Metrics

    GitHub repository

    Inspired by Prometheus (and Dropwizard metrics)
    (Reply with Prometheus format by default, and JSON (with application/json))

    Rationale
    This specification aims at providing a unified way for Microprofile servers to export Monitoring data ("Telemetry") to management agents and also a unified Java API, that all (application) programmers can use to expose their telemetry data.

    Releases

    @Counted
    - monotonic=false : nb ACTUEL d'executions concurrentes de la méthode
    - monotonic=false : nb TOTAL d'executions de la méthode
    @Gauge(unit = MetricUnits.MEGABYTES) : sampled value
    @Metered: durée moyenne
    @Timed: duration statistics
    @Metric:

    3 scopes (registres)

    Eclipse MicroProfile Open API

    GitHub repository

    Rationale
    This MicroProfile specification aims at providing a unified Java API for the OpenAPI v3 specification, that all application developers can use to expose their API documentation.
    → OpenAPI Specification de l'OpenAPI Initiative (OAI) ≈ dérivé de Swagger

    Releases

    Eclipse MicroProfile OpenTracing (distributed tracing)

    GitHub repository

    Rationale
    The MicroProfile OpenTracing specification defines behaviors and an API for accessing an OpenTracing compliant Tracer object within your JAX-RS application. The behaviors specify how incoming and outgoing requests will have OpenTracing Spans automatically created. The API defines how to explicitly disable or enable tracing for given endpoints.

    Releases

    → Zipkin implementation.

    Eclipse MicroProfile Rest Client

    GitHub repository
    How to deal with 4xx responses in MicroProfile Rest-Client

    Rationale
    The MicroProfile Rest Client provides a type-safe approach to invoke RESTful services over HTTP. As much as possible the MP Rest Client attempts to use JAX-RS 2.0 APIs for consistency and easier re-use.

    Releases

    Attachments

    Proudly Powered by Zim 0.75.2.

    Template by Etienne Gandrille, based on ZeroFiveEight and using JQuery Toc Plugin.