Kiuwan on premises is based on a client-server architecture that includes these major server components:
Kiuwan on premises can be deployed on a number of decentralized servers and accessed by users via HTTPS website.
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 | Provider | Default number of containers |
---|---|---|---|
kiuwan/apacheloadbalancer | loadbalancer | Kiuwan | 1 |
kiuwan/wildflykiuwan | wildfly-f[1-8] | Kiuwan | 1 |
wildfly-a[1-8] | 1 | ||
wildfly-s[1-4] | 1 | ||
kiuwan/updaterkiuwan | updaterkiuwan | Kiuwan | 1 (temporal) |
mysql:5.7.27 | mysql | Docker Official Images | 1 |
redis:5.0.5 | redis_0000[n] | Docker Official Images | 6 |
clustercreator | 1 (temporal) |
The following diagram shows the infrastructure that KoP installer will create by default:
The main purpose of each piece is (container names are shown between parentheses):
Depending on your needs, Kiuwan on premise 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.