How deeply does Quarkus in Action cover MicroProfile?

Defines platform and standalone specification sets, lists MicroProfile 6.1 contents, and notes TCK validation without detailing each API.

MicroProfile

As explained in Quarkus in Action

A coordinated release of a defined group of MicroProfile specifications under a single platform version.

MicroProfile is a community-driven set of open-source specifications for building cloud-native Java applications. Its platform coordinates a defined group of specification versions under one release number, while standalone specifications remain outside that bundle. section 10.1 section 10.8

The platform groups capabilities needed to operate distributed applications:

MicroProfile 6.1 includes Telemetry, OpenAPI, REST Client, Config, Fault Tolerance, Metrics, JWT Authentication, and Health. section 10.1
Standalone specifications include GraphQL, LRA, Context Propagation, Reactive Messaging, Reactive Streams Operators, and OpenTracing. section 10.1
Cloud-native patterns use these capabilities for health checks, metrics, distributed tracing, and fault tolerance. section 10.0 section 10.8

Quarkus compatibility and migration

Quarkus 3.15 aligns with MicroProfile 6.1, except for Metrics. Quarkus verifies specification compatibility with Technology Compatibility Kits, while applications using MicroProfile APIs can often migrate without reimplementing modules or changing code. section 10.1 section 1.2.3

How Quarkus in Action covers it

liveBook manning.com

Read Quarkus in Action on liveBook Get the book at manning.com

Related concepts

Quarkus platformused by · Quarkus is a Java framework for building cloud-native applications, optimized for containerized environments, fast startup, and low memory use.
MicroProfile Healthincludes · MicroProfile Health is a MicroProfile specification for exposing application health information through standardized health checks and endpoints.
OpenAPI specificationhas part · The OpenAPI Specification is a standard, machine-readable format for describing HTTP APIs, including their operations, inputs, outputs, data structures, and security requirements.
reactive messagingincludes · Reactive messaging is an asynchronous messaging approach in which messages are processed through reactive streams and communicated between application components or services.

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.