The FlowX Designer app is made up of a backend microservice and a frontend app. The backend microservice handles saving and editing process definitions. It provides the REST API used by the FlowX Designer. The processes defined here will be handled by the FlowX Engine.
Follow to next steps in order to set them up in your environment.
The backend microservice uses most of the same resources as the FlowX Engine:
Database - Postgres / Oracle
The backend microservice connects to the same Postgres / Oracle database as the Engine.
The backend microservice needs to be able to connect to the Kafka cluster in case you want to use the audit functionality. If connected to Kafka, it will send details about all database transactions on a configured Kafka topic.
It would be best if the FlowX Designer used a separate NGINX load balancer from the Engine. This it used in order to route API calls from the SPA (single page application) to the backend service, to the engine and to various plugins.
The FlowX Designer SPA will use the backend service to manage the platform via REST calls, will use API calls to manage specific content for the plugins and will use REST and WebSocket calls to connect to the engine.
Here's a suggested NGINX setup, the one used by us: