Kiuwan On-Premises (KoP) is based on a client-server architecture that includes these major server components:
Apache web server
Wildfly application server
Redis in-memory data store
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:
Kiuwan front: receives and answers HTTPS, HTTP or AJP requests (depending on your configuration) from the Apache web server (or directly from a client, depending on your configuration), both for the web application and REST API calls.
Depending on your needs, the Kiuwan On-Premises architecture supports both clustered environments and single-host installations. You can:
Keep all services in an all-in-one host installation.
Decide where each service will be installed, one by one (both Kiuwan services and infrastructure).
Externalize one, some or all of the provided non-Kiuwan services:
Apache load balancer
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.
As an example of the flexibility that the Kiuwan On-Premises installation tool provides, an alternative and possible configuration is depicted in the following image (Kiuwan Cloud and temporal services were ommitted to simplify the diagram):