Kiuwan On-Premises (KoP) is based on a client-server architecture that includes these major server components:

Kiuwan On-Premises can be installed on a single host or on multiple hosts (externalizing one, some or all of the provided infrastructure services).

You can also install Kiuwan On-Premises under your own AWS cloud, replacing the provided infrastructure services with compatible AWS services.

Kiuwan On-Premises and its roles

Kiuwan On-Premises defines three different roles for each instance:

The default installation will create a Kiuwan instance of each role.

Supplied services

All needed services are supplied as Docker containers. The following table summarizes all the available services:

Image nameServicesDefault number of containersMaximum number of containersProvider
kiuwan/apacheloadbalancerloadbalancer11Kiuwan
kiuwan/wildflykiuwanwildfly-f[1-8]18 
wildfly-a[1-8]18
wildfly-s[1-2]12
kiuwan/updaterkiuwanupdaterkiuwan1 (temporal)1
mysql:5.7.27mysql11Docker Official Images
redis:5.0.5

redis_0000[n]

66
clustercreator1 (temporal)1

The following diagram shows the infrastructure that KoP installer will create by default:

 

The main purpose of each piece is (service names are shown between parentheses):

Clustering support

Depending on your needs, the Kiuwan On-Premises architecture supports both clustered environments and single-host installations. You can:

All Kiuwan instance containers can be scaled up (to a limit) or down to the default configuration. This means that you can start more containers of each Kiuwan role depending on your load needs.