Red Hat · Software · YoctoIT tech page

JBoss & runtimes

Enterprise Java middleware and modern runtimes (Quarkus): the application foundations of half the industry.

FOCUS · THE JAVA THAT WORKSFrom EAP to Quarkus: making yesterday's Java run and writing tomorrow's well
Request the Free Assessment Learn more
YoctoIT material for clients and partners · Red Hat, RHEL, OpenShift, Ansible and the other products mentioned are trademarks of Red Hat, Inc. o di sue affiliate.
01 · What it is

JBoss EAP & Application Foundations, made clear.

Half of industry runs on Java: JBoss EAP is the enterprise application server that keeps it running supported — clustering, transactions, security. Application Foundations adds the modern runtimes: Quarkus for microservices (millisecond startup, reduced memory), Kafka for events, Keycloak for identity.

EAP 8
the supported application server: Jakarta EE, clustering, decade-long patches
Quarkus
cloud-native Java: -80% memory, instant startup, developer joy
Keycloak
SSO and identity: OIDC/SAML for the apps, standard and supported
JBoss EAP & Application Foundations
OFFICIAL RED HAT BRANDING · JBOSS & RUNTIMES
CONSOLE REALE · JBOSS EAP · FONTE: RED HAT DOCS
REAL CONSOLE · JBOSS EAP · SOURCE: RED HAT DOCS
02 · How to use it well

The things that make the difference.

The application foundations

The business applicationsERPs, portals, services
JBoss EAP
Quarkus
Kafka & Keycloak
solid legacy · fast new · events and identity
On OpenShift or RHELcontainers or traditional
Red Hat subscriptionpatches and support, not abandonment
Enterprise Java, with someone who answers

EAP updated and secure

6→7→8 migrations, patches and JVM tuning: the application server that doesn't end up in CVE bulletins.

Selective modernization

Not everything needs rewriting: the Migration Toolkit for Applications says what's worth moving to Quarkus.

From server to containers

EAP and the runtimes on OpenShift: S2I builds, health checks, scaling — Java goes cloud-native.

Centralized identity

Keycloak in front of the apps: corporate SSO, MFA and federation without reinventing auth.

03 · In depth

EAP 8, Quarkus and modernization

EAP 8 brings Jakarta EE 10 on a modular runtime (Wildfly core), with provisioning via Maven plugin and images optimized for OpenShift; the Migration Toolkit for Applications (MTA) analyzes the code and estimates the effort. Quarkus also compiles natively (GraalVM): millisecond startup and reduced memory for microservices; Kafka (AMQ Streams) and Keycloak (the RH SSO build) complete events and identity.

  • Jakarta EE 10 — the javax→jakarta namespace jump: MTA automates most of it
  • Provisioning Maven — the 'trimmed' EAP: only the subsystems the app uses
  • MTA — the static analysis that says what migrates easily and what doesn't
  • Quarkus nativo — GraalVM: ~0.02s startup for services that scale to zero
  • AMQ Streams — Kafka with an operator: declarative topics and users
  • Keycloak — OIDC/SAML for the apps: standard SSO without reinventing
04 · Numbers and lifecycle

The numbers that matter.

7+
years of support per EAP major
-80%
typical Quarkus memory vs the traditional stack
ms
native startup: the cold start that disappears
2
paths: EAP for the estate, Quarkus for the new
Enterprise Java modernizes by degrees: MTA to measure, EAP 8 to consolidate, Quarkus where speed is needed — with a single partner.
05 · Use cases

Where it really pays off.

Java ERPs

Mission-critical EAP apps managed and updated.

New microservices

Quarkus on OpenShift: the new born right from the start.

Event-driven integration

Kafka for the flows between systems, managed.

Java isn't legacy, it's heritage: we keep it solid and modernize it where it pays.