Kiuwan on premises 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 defines three different roles for each Kiuwan instance:
The default installation will create a Kiuwan instance of each role.
All needed services are supplied as Docker containers. The following table summarizes all the available services:
Image name | Services | Default number of containers | Maximum number of containers | Provider |
---|---|---|---|---|
kiuwan/apacheloadbalancer | loadbalancer | 1 | 1 | Kiuwan |
kiuwan/wildflykiuwan | wildfly-f[1-8] | 1 | 8 | |
wildfly-a[1-8] | 1 | 8 | ||
wildfly-s[1-2] | 1 | 2 | ||
kiuwan/updaterkiuwan | updaterkiuwan | 1 (temporal) | 1 | |
mysql:5.7.27 | mysql | 1 | 1 | Docker Official Images |
redis:5.0.5 | redis_0000[n] | 6 | 6 | |
clustercreator | 1 (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):
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.