Blueriq can be used in a hosting environment where high reliability is a requirement. This article will talk about the why, the when and the how of setting up Blueriq services in with aforementioned requirements in mind. With Blueriq your end users are using a Blueriq application that was designed in our design environment and it runs on a Blueriq Runtime instance. May it be a simple forms application, several webservices to an entire case management system. All of these Blueriq projects will be hosted and will be running through a Blueriq Runtime.

Why to Use Failover (Scalability vs. Availability vs. Reliability)

Let's first explore how Blueriq approaches the topic of high reliability. At this moment in time we decided to focus on reliability over availability and scalability, but without limiting the option to make your setup more available and/or scalable.

...

To make your Blueriq stack highly reliable we made Blueriq services store their state in external high performance data stores, in our case Redis. This way the components of Blueriq that have session management can be setup in a failover cluster, thus making your Blueriq stack more resilient against downtime.

When to Use Failover (What fits your requirements?)

Blueriq usually runs in an landscape with multiple other hosted applications. The documentation about the subject failover is primarily meant to advise on when and how to use failover. We offer certain functionality and it is up to the professionals implementing the solution to make the decisions on how to use functionality in this solution. How does Blueriq fit in your infrastructure? What technical requirements do you have as a team and organization?

...

* Switching to newer major versions of Blueriq components might still require you to have downtime.

How to Use Failover (Clustering Runtimes)

Setting up Blueriq to support failover scenarios requires you to set up clusters of your Blueriq services.

...