Overview of the System Architecture

QueryPie operates on a web application architecture designed to function seamlessly in both cloud and on-premises environments.

In the case of QueryPie, it is commonly deployed as a Docker container on a Linux virtual machine (VM). It is recommended to run QueryPie as a web application protected by Transport Layer Security (TLS) certificates. When deploying QueryPie in a cloud environment, it is recommended to configure it with a Load Balancer and TLS certificate.

Essential resources for QueryPie operation, such as connection settings and user data, are stored in a MySQL database. Redis serve as temporary storage to ensure rapid response times.

The binary package, provided as a Docker image, is versatile and deployable on Linux VMs in Azure, AWS, GCP, or on physical Linux machines, provided that the OS and Docker daemon are up-to-date. QueryPie also offers native support for Kubernetes, although we primarily recommend it for customers with a Kubernetes DevOps team. The version provided to our customers is identical to the one available in the product. The features of the product are determined by the installed license, which will be remotely provided and installed by us. Evaluation licenses typically restrict usage to 4 to 6 weeks, while a commercial license offers a duration of approximately 12 to 13 months.

Simple System Configuration for Evaluation

The system architecture outlined above represents a simplified configuration setup for testing and evaluating the QueryPie product. Users access QueryPie through a web browser, with QueryPie operating on a single Linux VM connected to an Application Load Balancer (ALB). Within the Linux VM, the QueryPie application runs within Docker containers, while a MySQL database and a Redis cache utilized by QueryPie also run within Docker containers.

QueryPie will be accessible via a web service URL with a TLS certificate applied, such as https://querypie-poc.customer.com/. To configure this setup, it is recommended to establish an ALB along with the TLS certificate.

Prerequisites for Evaluation Setup

To install QueryPie for testing and evaluation, you'll need to prepare the following:

1. A Fully Qualified Domain Name (FQDN) for the product.

   • For example, querypie-poc.customer.com. However, feel free to choose your own.

2. A TLS certificate for the above FQDN, to be managed by the Load Balancer(LB).

   • QueryPie requires a Load Balancer (LB) with TLS. You will not need direct access to the TLS certificate file.

   • For AWS, it is Application Load Balancer.

   • For Azure, it is Application Gateway.

   • For GCP, it is Application Load Balancer.

3. A Linux VM that will run QueryPie as Docker containers.

   • A computing size of 2 vCPUs and 8GiB of memory is recommended for evaluation purposes.

   • Applying a Load Balancer is necessary, but you do not need to configure 2 or more VM instances. Even with QueryPie installed on a single VM, you can still effectively test the product's functionality.

4. Remote access to your Azure environment for temporary use, which includes:

   • Provision of a temporary Azure account for setting up the Load Balancer and TLS.

   • Configuration of a Linux VM instance accessible via an SSH public key.

Summary of System Architecture for Real Use

The configuration outlined above provides a condensed overview of the essential elements of the system architecture applicable when utilizing the QueryPie product in real-world scenarios. Users can access QueryPie via a web browser. Additionally, QueryPie Agent can be installed on users' PCs to enable access databases and systems from applications running on their PCs, such as DataGrip, MySQL Workbench, iTerm, Putty, and more.

In a cloud environment, the QueryPie server is configured with a redundant setup to function as a web application. It is recommended to utilize Managed Service-based MySQL and Redis provided by the cloud. The QueryPie Agent installed on PCs connects to the QueryPie server using its proprietary TCP-based protocol, and it is recommended to configure a Network Load Balancer for this purpose.

Please note that the above system configuration serves as a summarized representation intended to facilitate user comprehension and is not a detailed system architecture.