​

How NGINX is working?

NGINX allows you to hide a server application’s complexity from a front-end application. It uses an event-driven, asynchronous approach to create a new process for each web request, with requests handled in a single thread.

​

Using NGINX with FlowX Designer

The NGINX Ingress Controller for Kubernetes - ingress-nginx is an ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.

Ingress allows you to route requests to services based on the host or path of the request, centralizing a number of services into a single entry point.

The ingress resource simplifies the configuration of SSL/TLS termination, HTTP load-balancing, and layer routing.

For more information, check the following section:

​

Integrating with FlowX Designer

FlowX Designer is using NGINX ingress controller for the following actions:

1. For routing calls to plugins
2. For routing calls to the FlowX Engine:

• Viewing current instances of processes running in the FlowX Engine
• Testing process definitions from the FlowX Designer - route the API calls and SSE communications to the FLOWX engine backend
• Accessing REST API of the backend microservice

3. For configuring the Single Page Application (SPA) - FlowX Designer SPA will use the backend service to manage the platform via REST calls

In the following section, you can find a suggested NGINX setup, the one used by FlowX.AI:

​

Installing NGINX Open Source

For more information on how to install NGINX Open Source, check the following guide: