Versions Compared

Old Version 5

changes.mady.by.user Mihai Bob

Saved on

compared with

New Version Current

changes.mady.by.user Menno Gülpers

Saved on

Key

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

Introduction

This article chapter describes what infrastructure is needed in order to run Blueriq Runtime in a clustered environment.

A cluster is a group of multiple server instances, spanning across more than one node, all running identical configuration. All instances in a cluster work together to provide high availability, reliability, and scalability.

Minimum Hardware and Software Requirements

Each paragraph described below is a software requirement that is assumed to be running in it's own node, or even on multiple nodes where applicable.

The use case described in this section, the Runtime cluster consists of the following entities:

  • Two instances of Blueriq Runtime ( running on two identical nodes)
    • An instance of Redis server (running on a separate node)

    Table of Contents

    Image Added

    Load balancer

    A reverse proxy for load balancing HTTP requests

    (running on a separate node)
    • used to distribute network application traffic across a cluster of servers improving responsiveness and availability of applications

    for the Blueriq runtime is needed. It also runs in it's own separate node.

    Blueriq does not specify a specific load balancer to be used, but for following chapters regarding clustering, nginx will be used as example.

    Blueriq Runtime

    Two or more Blueriq Runtimes running each of them on different nodes with the same configuration.

    Documentation on how to set up the runtime for cluster configuration can be found here.

    Key-Value store server

    A Redis server (Key-Value store server)

    Each paragraph described below is assumed to be running on different nodes.

    Redis Server

    A Redis server

    running in it's own node is required for running Blueriq in a clustered environment. It is used by the Blueriq Runtime for storing and retrieving data about the currently logged in user, and applications current state.

    Info

    Redis is the default in-memory data structure store supported by Blueriq. For using other in-memory data store and how to add support for them in runtime can be found here.

    Blueriq Runtime

    Two or more Blueriq Runtimes running each of them in different nodes with the same configuration.

    Documentation on how to set up the runtime for cluster configuration can be found here.

    A reverse proxy

    A reverse proxy for load balancing HTTP requests for the Blueriq runtime is needed. It also needs to run in it's own separate node.

    Blueriq does not specify a specific load balancer to be used, but for future articles regarding clustering, nginx will be used as example.

    Panel
    Section
    Column
    width50%

     Previous: Runtime cluster

    Column

    Next: 2. About the load balancer