Introduction

The CoreOne Suite Next-Gen Workflow Service is an independent service that can either be installed on a single server or multiple servers environment.

Data Storage

All the necessary data to run the Next-Gen Workflow Service is stored in the CoreOne Suite Meta Directory. The CoreOne Suite Next-Gen Workflow Service therefore needs direct access to the CoreOne Suite Meta Directory.

Communication

As the Workflow Service interacts with the Application Service, communication in both ways have to be established. The Workflow Service uses the Application API to execute actions and offers an own API. This API is used by the Application Service as well as third-party applications and services.

Multi Server Deployment

In a multi server deployment the following services are needed.

Message Broker

By default this is a RabbitMQ. This can be installed on the same server as the Next-Gen Workflow Service Node or on a dedicated server or cluster.

Distributed Lock Provider / Distributed Cache Signal Provider

As the distributed lock provider and the distributed cache signal provider, we use Redis. This can be installed on the same server as the Next-Gen Workflow Service Node or on a dedicated server or cluster.