Skip to main content

High Availability in Klaw

Ensuring High Availability is crucial when deploying any application in a production environment. High Availability mode guarantees minimal or no downtime and balanced processing of requests.

Klaw, a Java-based web application, can be deployed in High Availability mode. A key feature of Klaw is its ability to reset the cache in all running instances whenever users or administrators request changes.

Why is High Availability important?

To minimize interruptions and downtime, it is crucial to prepare for unforeseen events that can cause server failures. Emergencies can potentially bring down even the most reliable software and systems. Implementing highly available systems can reduce the impact of such events, as these systems often can automatically recover from failures in components or servers.

High Availability architecture

Ensuring systems can handle higher workloads and substantial traffic is undeniably vital. However, it is equally important to identify potential failure points and minimize downtime. A key component in achieving this goal is a highly available load balancer, which plays a significant role. It involves implementing a scalable infrastructure design that adapts to increased traffic demands. This often involves employing a software architecture that surpasses hardware limitations.


How to configure and enable High Availability

In the Klaw Core module, configure the below property, which is a comma-separated list of Klaw instances.


This configuration will make sure of any cache which has to be reset on the instances.

Next Configure the secure communication between the multiple instances of Klaw.

# This allows App2App communication in a HA setup
# where multiple Klaw-core instances are deployed
# Provide a base 64 encoded string. The same secret should be used in all Instances.
# Update the below to your own unique secret!!!!!

# Enable High Availability for multi-instance Klaw-core deployment.
# Set to true to enable/false to disable