Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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 Kiuwan instance:

  • Kiuwan front: receives and answers HTTPS requests, both for the web application and REST API calls.
  • Kiuwan analyzer: processes analysis results asynchronously.
  • Kiuwan scheduler: processes background tasks such as notifications and Kiuwan Insights database updates.

...

  • Apache (loadbalancer): an Apache instance that balances the traffic between Kiuwan frontals (kept in the default installation to allow easy frontal scaling).
  • Kiuwan front (wildfly-f1): a Kiuwan frontal.
  • Kiuwan analyzer (wildfly-a1): a Kiuwan analyzer.
  • Kiuwan scheduler (wildfly-s1): a Kiuwan scheduler.
  • MySQL (mysql): the main Kiuwan database.
  • Redis cluster (redis_0000[n]): redis store nodes. Used , used by Kiuwan as a data cache.
  • Redis cluster creator (clustercreator): a temporal redis container that configures each Redis node as a cluster.
  • Kiuwan updater (updater): a temporal Kiuwan instance that installs, updates and upgrades needed data or configuration.

...

  • Keep all services in an all-in-one host installation.
  • Under AWS, decide where each service will be installed, one by one (both kiuwan Kiuwan services and infrastructure, as long as you use AWS elasticache as Redis cluster).
  • Externalize one, some or all of the provided non-Kiuwan services:
    • Apache load balancer
    • MySQL
    • Redis

...