Tomcat/TomEE Cluster Hosting on MassiveGRID PaaS
The Tomcat/TomEE Cluster with High Availability deploys several Apache Tomcat or TomEE nodes with HTTP session replication behind an NGINX load balancer on MassiveGRID PaaS. Java web applications gain failover and horizontal scaling without code changes, and nodes are added automatically under load.
Tomcat/TomEE Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $44.28 a month for the Starter configuration, a NGINX load balancer (256 MiB) and 2 × Application node (1 GiB each), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with Tomcat/TomEE Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Tomcat/TomEE Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | Tomcat/TomEE cluster with High Availability |
| Type | Application (installs a complete environment) |
| Category | Clusters & Containers |
| Software vendor / project | Apache Software Foundation |
| Licence | Apache License 2.0 (open source) |
| Runtime / stack | Apache Tomcat or TomEE nodes with session replication behind an NGINX load balancer |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $44.28/month for the Starter configuration (18 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Tomcat/TomEE Cluster?
Apache Tomcat is the most widely used Java servlet container, and TomEE is Tomcat extended into a certified Jakarta EE web-profile server. Both run the vast majority of Java web applications, including Spring MVC and Spring Boot WARs. Clustering them means putting a load balancer in front of several instances and replicating sessions so a user is not logged out when a node fails or is removed.
The package configures Tomcat's cluster membership and session replication, deploys the NGINX balancer with sticky sessions and health checks, and enables horizontal auto-scaling. New nodes join the cluster and the balancer automatically. You deploy the same WAR to every node from the dashboard or through Git.
What the Tomcat/TomEE Cluster Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Tomcat or TomEE nodes: Two or more Java application server containers with clustering and session replication enabled, your choice of Tomcat or TomEE.
- NGINX load balancer: A balancer distributing requests with sticky sessions and health checks, terminating SSL.
- Auto-scaling triggers: Rules that add and remove application nodes on CPU or memory load and update the balancer.
- Synchronised deployment: Applications deployed via the dashboard or Git are pushed to every node in the cluster.
What Tomcat/TomEE Cluster Costs to Run
Three starting configurations for the Tomcat/TomEE Cluster package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterDevelopment | NGINX load balancer (2 cloudlets, 256 MiB), 2 × Application node (8 cloudlets, 1 GiB each) | 18 | $44.28 |
| StandardProduction | NGINX load balancer (4 cloudlets, 512 MiB), 2 × Application node (16 cloudlets, 2 GiB each) | 36 | $88.56 |
| ProductionHigh traffic | NGINX load balancer (4 cloudlets, 512 MiB), 4 × Application node (16 cloudlets, 2 GiB each) | 68 | $167.28 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
Why Teams Choose Tomcat/TomEE Cluster
Session failover
Replicated sessions keep users logged in when a node fails or is scaled away.
Zero-code scaling
Existing WAR files run unchanged; the cluster handles distribution.
Tomcat or TomEE
Choose plain Tomcat for servlet and Spring applications or TomEE for Jakarta EE web profile features.
Lightweight
Tomcat nodes start in seconds and run well on small cloudlet allocations, keeping the cluster economical.
How to Install Tomcat/TomEE 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 Tomcat/TomEE 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 Tomcat/TomEE Cluster node, wires them together and hands you the live URL and credentials.
Who Runs Tomcat/TomEE Cluster on PaaS
Spring and servlet applications
Java web apps packaged as WARs that need high availability.
Customer-facing portals
Applications with login sessions that must survive node failures.
Replacing single-server Tomcat
Teams whose one Tomcat box has become a risk or a bottleneck.
Why Run Tomcat/TomEE Cluster on MassiveGRID PaaS
Built for uptime. Tomcat/TomEE 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 Tomcat/TomEE 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 27001 and 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.
Tomcat/TomEE Cluster Questions
Tomcat/TomEE Cluster Guides from the MassiveGRID Blog
Scenario-driven guides on running Tomcat/TomEE Cluster on MassiveGRID PaaS, written for the developers, operators and buyers who deploy it. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside Tomcat/TomEE Cluster, or that solve the same problem a different way. Browse all 83 packages.
Deploy Tomcat/TomEE Cluster Today
Start the free 14-day trial and have Tomcat/TomEE Cluster running in minutes. No credit card required.