Java Cloud Hosting: Elasticity and Flexibility in a Turnkey PaaS

This guide acquaints you with the distinctive features of Java hosting within the Unispace platform and lets you easily get started with a broad functionality list.

Java Versions

There are following Java versions and distributions available at Unispace:

You can choose the preferred version while creating an environment, or change it later.

Java Application Servers

Within a wide variety of software stacks, Unispace supports a pure Java Engine and the following Java application servers:

  • GlassFish
  • Jetty
  • Payara
  • Spring Boot
  • Tomcat
  • TomEE
  • WildFly

Java Environment Creation

To host a Java application, you need to create an appropriate environment. Just open the topology wizard in your Unispace dashboard, navigate to the Java language tab, pick the desired Java application server, databases, and other stacks. If needed, customize settings (such as cloudlets, disk space, region, etc.) and click Create.


Java Cloud Hosting

All added servers represent fully isolated containers, located on different hosts for more availability, while isolation eliminates the risks of interfering with one another. You can attach the Public IP address to any of these servers for being accessed directly. Otherwise (i.e. if using default settings), the incoming requests sent to your application will be proxied by Shared Load Balancer.

Java Application Deployment

After environment creation, you can deploy your Java application. Herewith, Unispace PaaS fully automates the deployment process allowing you to get the project up and running effortlessly.

The following deployment methods are supported:

  • via the application archive –, and .ear archives
  • from the GIT/SVN remote repository, using the Maven build node
  • using plugins – Ant TaskEclipseIntelliJ IDEAMaven and NetBeans
Java App Deployment


Domains Management

You can bind a custom domain name to your application’s URL and use it instead of the default environment domain:

  • CNAME redirect if using Shared Load Balancer; is recommended for dev and test environments
  • DNS A Record if using public IP; can handle high traffic load and is suitable for production environments

Also, with the help of the swapping domains feature or the SwapExtIps API/CLI method, you can upgrade and modify your application with zero downtime (i.e. your users won’t notice any interruption).

Automatic Vertical Scaling

Unispace PaaS dynamically provides the number of cloudlets (i.e. RAM and CPU resources), which are required by your application to handle the current load. Just specify the maximum limit, and everything else will be performed by the platform automatically – no manual intervention required. This feature is called automatic vertical scaling and ensures that you never overpay for unused capacities without experiencing a resource shortage.

Pay Per Use

To set or change the vertical scaling limit, just use the appropriate slider within the topology wizard:

Horizontal Scaling: Manual and Automatic

In case your application becomes highly popular and a single node is not enough, feel free to scale it horizontally. Herewith, to ensure even more reliability and high-availability, all the newly added nodes are created on the different hardware nodes.

Click the +/- buttons within the Horizontal Scaling section of the topology wizard to set the required number of nodes (load balancer will be added automatically).

Also, you can adjust the preferred scaling mode:

  • Stateless – simultaneously creates all new nodes from the base image template
  • Stateful – sequentially copies file system of the master container into the new nodes

Horizontal scaling can be performed not only manually but also automatically based on the current load on the node, which is monitored through the tunable triggers.

Within the Settings > Monitoring > Auto Horizontal Scaling section, you can adjust the scaling conditions due to your needs, i.e. the lower/upper limit (percentage) for the specified resource type during a certain period. If the load stays out of the set limits, the nodes removal/addition process will be called automatically.

There are five different types of resources, which are monitored by triggers:

  • CPU
  • Memory (RAM)
  • Network
  • Disk I/O
  • Disk IOPS
Java Scaling triggers

The trigger starts monitoring the resource consumption immediately after addition, and when the usage level exceeds the stated limit, a trigger becomes invoked. Subsequently, if the load persists for a defined period, it will be executed, adjusting the number of nodes.

Java Clusterization

The embedded application server clustering feature provides replication of sessions between pairs of nodes and eliminates the necessity of additional software or Memcached usage for increasing application availability.

Unispace provides automated session replication between Tomcat and TomEE servers with the help of multicast to gain web application high availability within the Java cluster. This High-Availability feature can be enabled in the wizard during environment creation or topology tuning.

Java Clusterization

Herewith, the newer modern Auto-Clustering solution is provided for the GlassFishPayara, and WildFly stacks:

  • Out-of-Box GlassFish & Payara Clustering
  • WildFly Automatic Micro Clustering and Scaling


Java Cluster

Database Connection to Java Application

A set of scalable and fully manageable database servers can be easily installed within the Java environment. To establish the connection, adjust your application following the instruction based on the database you require:

  • MySQL and MariaDB Connection
  • PostgreSQL Connection
  • MongoDB Connection

Unispace PaaS provides high-quality Java hosting with improved availability, redundancy, and scalability strengths for your application.

Martin Brendl

Martin Brendl

Leave a Replay

Sign up for our Free Trial

Unispace provides a free trial of it’s services for 14 days. No Credit Card required.

Scroll to Top