Red Hat JBoss Enterprise Application Platform
Application serverjboss-eap
Red Hat's supported Jakarta EE application server, the commercial build of WildFly.
- Provider
- default
- Category
- Compute
- Also known as
- EAP
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | inherited |
| clustering | boolean | — | no | false | inherited |
| configurationProfile | enum | standalone | standalone-ha | standalone-full | standalone-full-ha | no | standalone | inherited |
| criticality | enum | low | medium | high | no | medium | inherited |
| instancePerEntity | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| jakartaProfile | enum | web-profile | core-profile | full-platform | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| operatingMode | enum | standalone | domain | no | standalone | inherited |
| ownsData | boolean | — | no | true | inherited |
| runtime | string | — | no | — | ▸ jvm |
| shardingStrategy | enum | none | consistent-hash | range | lookup | no | none | inherited |
| singleWriter | boolean | — | no | false | inherited |
| stateless | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
external-call-inline-without-durable-path
A service that calls a third party synchronously, with no queue or workflow engine attached, has nowhere to park the request when the third party is slow or down. The failure becomes the user's problem instead of a retried job.
- — all of these hold:
- — the node has at least one synchronous outgoing edge to a third-party-api
- — this does not hold:
- — the node has at least one connected edge joining a workflow-engine or queue
fanout-inline-in-request-path
Calling a worker synchronously puts the background job on the request path. The caller waits for the slowest part of the fan-out.
- — the node has at least one synchronous outgoing edge to a worker
stateful-hash-ring-without-ring-manager
A stateful service on a consistent hash ring needs something that owns the ring: detect a dead host, pick a replacement, tell everyone. Without a coordination service the ring is edited by hand during the outage.
- — all of these hold:
- — the node's `shardingStrategy` is "consistent-hash"
- — this does not hold:
- — the node has at least one connected edge joining a coordination-service
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "jboss-eap", component: "jboss-eap" }Elastic Container Instancealibaba-eciEnterprise Distributed Application Servicealibaba-edasFunction Computealibaba-function-computeServerless App Enginealibaba-saeYIDAalibaba-yidaAWS App Runneraws-app-runnerAWS App Studioaws-app-studioCloudFront Functionsaws-cloudfront-functionsAWS Elastic Beanstalkaws-elastic-beanstalkAWS Fargateaws-fargateAmazon GameLift Serversaws-gameliftLambda@Edgeaws-lambda-edgeAmazon S3 Object Lambdaaws-s3-object-lambdaAWS Transfer Familyaws-transfer-familyAWS LambdalambdaAzure App Serviceazure-app-serviceAzure AI Bot Serviceazure-bot-serviceAzure Container Appsazure-container-appsAzure Container Instancesazure-container-instancesMicrosoft Copilot Studioazure-copilot-studioAzure Functionsazure-functionsHealthcare agent serviceazure-health-botMicrosoft Power Appsazure-power-appsAzure Spring Appsazure-spring-appsDynamic Workerscloudflare-dynamic-workersEmail Workerscloudflare-email-workersCloudflare Pagescloudflare-pagesCloudflare Sandbox SDKcloudflare-sandboxCloudflare Workerscloudflare-workersWorkers for Platformscloudflare-workers-for-platformsGeneric application serverapp-serverAutoGen Studioautogen-studioBotpressbotpressCloud Foundrycloud-foundryContainer servicecontainer-serviceCoolifycoolifyCrewAI AMPcrewai-enterpriseDifydifyDocker containerdocker-containerDokkudokku
and 58 more → Application server page# yaml-language-server: $schema=../../schema/component.schema.json # Red Hat JBoss Enterprise Application Platform: the supported build of WildFly. "Introduction to # Red Hat JBoss EAP" states 8.0 is compatible with the Jakarta EE 10 Web Profile, Core Profile and Full # Platform and runs either as a standalone server or in a managed domain; the "Configuration Guide" says # standalone.sh uses standalone.xml by default, so clustering subsystems are not loaded unless chosen. schemaVersion: "1" type: "component" id: "jboss-eap" kind: "app-server" provider: "default" docs: "https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/8.0/html-single/configuration_guide/index" aliases: ["EAP"] defaults: managed: false runtime: "jvm" properties: operatingMode: type: "enum" values: ["standalone", "domain"] default: "standalone" configurationProfile: type: "enum" values: ["standalone", "standalone-ha", "standalone-full", "standalone-full-ha"] default: "standalone" jakartaProfile: type: "enum" values: ["web-profile", "core-profile", "full-platform"] clustering: type: "boolean" default: false