Technical Specifications

Hardware specifications
required for our cloud architecture

Below, the technical specifications for a private cloud with architecture are described.

Required Hardware

Starter Configuration

Your company can start with a single application server for a range of 50–500 users, depending on the number of transactions. To increase capacity, just add a new application server. The Load Balancer (see below) will take care of workload distribution among servers.


Medium/High Configuration

Because our applications are built using multi-tenant SaaS architecture, they can easily be scaled by adding further application or database servers. With this architecture, Axional products can handle tens of thousands of users.


Operating System

Our applications work on industry-standard operating systems. Please see the table in the sidebar for supported operating systems for both Java Application Servers (JAS) and database servers.

Load Balancing

A software load balancer distributes network or application traffic across a number of servers, increasing the capacity (number of possible concurrent users) and reliability of your applications.

Application servers work as a cluster. So, in case of failure of one of the servers, the process load is distributed across the remaining servers, shielding users from the hardware issue at hand.

Examples of open-source load-balancing software projects you can use include:

  • PEN: Simple to configure, offers basic features (link)
  • HAProxy: Recommended. Supports almost every feature companies could want from a load balancer. (link)

System Authentication and Security

In addition to native authentication for database registered users, our application server core also offers LDAP and Windows Active Directory validation. Apache Tomcat valves con also be used to achieve an SSO experience (read more on this entry in our blog).

Method Type SSO
Native (database config.) App. core No
LDAP App. core No
Windows Active Directory App. core No
Tivoli Tomcat valve Yes