WildFly Cluster on MassiveGRID PaaS
The WildFly Managed Domain Cluster deploys WildFly in managed domain mode on MassiveGRID PaaS: a domain controller that holds configuration and deployments, worker hosts that run your Jakarta EE applications, and a load balancer in front. Auto-scaling adds worker hosts under load and the domain controller configures them automatically.
Both buttons open the MassiveGRID PaaS dashboard with WildFly Cluster pre-selected. The trial needs no credit card.
WildFly Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | WildFly Managed Domain Cluster |
| Type | Application (installs a complete environment) |
| Category | Clusters & Containers |
| Software vendor / project | Red Hat (WildFly community project) |
| Licence | LGPLv2.1 (open source) |
| Runtime / stack | WildFly domain controller, worker hosts, load balancer |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is WildFly Cluster?
WildFly is the open-source upstream of Red Hat JBoss EAP and one of the fastest, most modular Jakarta EE application servers. In managed domain mode, a domain controller manages many hosts centrally: deploy an application to a server group once and every server in the group receives it, change a datasource once and it propagates. Clustering adds HTTP session replication and distributed caching through Infinispan.
The package builds the domain, joins the worker hosts, configures the load balancer with health checks and sets auto-scaling triggers. It is the right choice for teams that want JBoss-style operations with elastic infrastructure, and it pairs with the WildFly Continuous Deployment package for Git-driven releases.
What the WildFly Cluster Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- Domain controller: The WildFly management node holding domain configuration, server groups and deployments, with the admin console exposed over HTTPS.
- Worker hosts: WildFly host controllers running server instances in a cluster-enabled profile, scaled horizontally on load.
- Load balancer: A balancer in front of the worker servers with sticky sessions and health checks.
- Auto-scaling: New hosts register with the domain controller, receive configuration and deployments, and join the balancer automatically.
Why Teams Choose WildFly Cluster
Central management
One console and CLI for configuration, deployments and monitoring across every host.
Session replication
Infinispan-backed HTTP session clustering keeps users logged in through failures and scale-downs.
Jakarta EE and MicroProfile
Full platform support plus MicroProfile APIs for microservices.
JBoss EAP compatible
Applications and configuration move between WildFly and Red Hat JBoss EAP with minimal change.
How to Install WildFly Cluster on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the WildFly Cluster package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every WildFly Cluster node, wires them together and hands you the live URL and credentials.
Who Runs WildFly Cluster on PaaS
Enterprise Java estates
Organisations standardised on JBoss/WildFly that want elastic capacity.
Mission-critical web applications
Systems that need session failover and rolling deployments across many servers.
Migration from JBoss EAP
Teams moving from licensed EAP to open-source WildFly without losing domain-mode operations.
Why Run WildFly Cluster on MassiveGRID PaaS
Built for uptime. WildFly Cluster runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet WildFly Cluster environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Platform as a Service.
WildFly Cluster Questions
More from the Marketplace
Packages that are often deployed alongside WildFly Cluster, or that solve the same problem a different way. Browse all 84 packages.
Deploy WildFly Cluster Today
Start the free 14-day trial and have WildFly Cluster running in minutes. No credit card required.