Flow components

Flow server is a combination of several components:

Flow UI provides the front-end capability

Flow API provides all of the REST endpoints and the ability to execute Taxi queries and expose Taxi queries as REST endpoints

Flow stream capability executes Jet Jobs when a streaming query is published as a REST or websockets endpoint

Flow uses a Postgres database to store Query History and usage information.

Flow supports pulling the project configuration from one or more Git repositories. This is useful for environments where there is no persistent storage, and is recommended for production. For information on configuring a Git repository, see Connect a Git Repository.

In production, a load balancer is used to distribute traffic across multiple instances of Flow server. This is useful for scaling out the number of instances to handle more traffic. For more information on configuring a load balancer, see Load Balancer.

Prometheus is an open-source monitoring and alerting toolkit. Flow exposes metrics that can be scraped by Prometheus. For more information on configuring Prometheus, see Observability.