Versions Compared

Old Version 7

changes.mady.by.user Felix Janssen

Saved on

compared with

New Version 8

changes.mady.by.user Geert Graat

Saved on

Key

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

Include Page
_DcmArchitectureBetaLabel
_DcmArchitectureBetaLabel

Table of Contents

Scaling/availability

Blueriq services

  • For the beta version, delivered with Blueriq 15.0, we support a single instance of each component described in the Blueriq DCM architecture overview.
  • In the first non-beta version (release date not known yet), we will support two scalability aspects:
    • Multiple runtimes for user interaction, with sticky sessions
    • Execute automatic tasks in parallel on a single runtime AND use multiple runtimes for executing automatic tasks
  • In the further future, we intend to support:
    • Multiple runtimes for user interaction with external sessions (Redis)
    • Multiple case engines
    • ...?

Third party services

Scaling/availability for third party services (RabbitMQ, MongoDB, Oracle/MSSQL) needs to be configured in these applications. Each of them provides information on how to scale:

Third party softwareLink
RabbitMQhttps://www.rabbitmq.com/clustering.html
MongoDBhttps://www.mongodb.com/basics/scaling
Oracle databasehttps://blogs.oracle.com/exadata/post/horizontal-scaling-with-oracle-database
MSSQLhttps://docs.microsoft.com/en-us/previous-versions/msp-n-p/dn589797(v=pandp.10)

Backup strategy

Blueriq stores operational data in several databases. You are advised to back up this data, otherwise cases might get corrupt after e.g. a server crash.

SQL (MSSQL/Oracle)

Use the backup capabilities of these platforms that conform to your need. You need to back up:

  • process database
  • scheduler database
  • timeline database
  • trace database
  • comments database
  • aggregate database

MongoDB

Use the backup capability of this platform. You need to back up:

...

* It is possible to restore the DCM Lists Database from the process database, but this process may take some time, depending on the number of processes in the process database

RabbitMQ

See https://www.rabbitmq.com/backup.html for information. As the data in RabbitMQ changes rapidly, there is probably no secure way to back up data at any given time. You would need to hope that the data concerning messages that were in RabbitMQ at the moment that the server on which it runs crashed is not corrupted.

...

We advise to combine all exchanges/queues for the DCM setup in a single RabbitMQ virtual host.

Security

For the runtime(s) that have user interaction, we advise to protect them as you would with any Blueriq Runtime. See Security for more information.

...