Skip to main content
This article moved to workflowserver.io permanently.

Workflow Server

Workflow Server is a ready-to-use Workflow Engine-based application with an admin panel that you can deploy into your infrastructure. It can be integrated with NodeJS, PHP, Ruby, .NET, or Java applications via a REST API. Workflow Server is a key component for managing the lifecycle of business objects within your enterprise. Workflow Server supports all the functions of Workflow Engine.

Workflow Server Architecture

How to launch​

You can read instructions on how to launch Workflow Server here.

Integration​

Workflow Server has a set of two APIs for integration:

  • Workflow API - allows you to create processes and set their states.
  • CallBack API - allows you to include additional actions and conditions to the workflow, and get notifications on workflow state changes.

Workflow Server can be used in a microservice architecture, integrated via a bus or directly with your application. You can read more on that here.

We have prepared a swagger description for our APIs.

Performance​

Workflow Server can process about 200 requests per second on a typical 4 GB RAM server. The response time of a single request is about 20ms. Performance does not degrade with up to several million records with default database server settings. Custom database server settings are required for larger volumes of data. Performance can vary drastically depending on your schemes. We have prepared SoapUI tests so that you can test performance yourself. You can download them here. Please, note, that Workflow Server without a license key processes data in a single thread.

Scalability​

Workflow Server is a stateless server, so you can deploy several Workflow Server instances. If you face database server performance issues, please use horizontal scaling options, recommended by your database vendor. To balance the load between Workflow Server instances, we recommend using Nginx. Please, note: when deploying a multiserver configuration you need to select one master server which will handle all timer events and set the DisableTimeManager parameter of other servers to true.

Authorization​

Workflow Server does not have internal mechanisms of authorization and authentication. We recommend deploying Workflow Server in a DMZ or use a firewall to restrict access.

System requirements​

  • OS Windows/Linux/macOS
  • CPU 1 core 1 GHz
  • RAM 1 GB
  • HDD/SSD 5 GB
  • .NET Core Runtime 2.0