System Architecture Overview

Overview

QueryPie features a web application architecture that operates in both cloud and on-premises environments.

QueryPie typically runs as a Docker container on a Linux VM, and it is recommended to operate it as a web application secured with TLS certificates. When customers install and operate QueryPie in a cloud environment, it is advised to configure it with a load balancer and TLS certificates. Resources required for QueryPie operations, such as connection settings and user information, are stored in a MySQL database. Redis is utilized as a temporary storage solution for faster response times.

The binary package of QueryPie is created as a Docker image and is prepared for deployment on Linux VMs in Azure, AWS, GCP, or physical Linux servers, provided that the OS and Docker daemon are up to date. Although QueryPie natively supports Kubernetes, it is primarily recommended for customers with Kubernetes DevOps teams. The trial evaluation binary package is identical to the version provided to customers. The product's features are managed by an installed license provided and remotely managed by the supplier. Evaluation licenses are typically valid for 4 to 6 weeks, while commercial licenses offer a usage period of approximately 12 to 13 months.

Simple Configuration for Evaluation

The system architecture above is a simplified configuration example for evaluating the QueryPie product. Users connect to QueryPie via a web browser, and QueryPie operates on a single Linux VM connected to an Application Load Balancer. Within the Linux VM, the QueryPie application runs as a Docker container, alongside the MySQL database and Redis cache used by QueryPie, also running as Docker containers.

QueryPie is accessed through a web service URL with a TLS certificate, such as https://querypie-poc.customer.com/, and it is recommended to set up an Application Load Balancer with a TLS certificate to configure this.

Prerequisites for Evaluation Setup

The following are the prerequisites for installing QueryPie for testing and evaluation purposes:

• Fully Qualified Domain Name (FQDN) for Product Access:

  • You can freely choose a preferred domain. Example: querypie-poc.customer.com.

• Load Balancer (LB) and TLS Certificate for the Above FQDN:

  • QueryPie technical support staff do not need direct access to TLS certificate files.

  • However, QueryPie requires a load balancer with TLS applied.

  • For AWS, this is the Application Load Balancer.

  • For Azure, this is the Application Gateway.

  • For GCP, this is the Application Load Balancer.

• Linux VM to Run QueryPie:

  • For evaluation purposes, it is recommended to use a VM with 2 vCPUs and 8 GiB of memory.

  • While applying a load balancer is essential, there is no need to configure more than one VM instance.

  • QueryPie can effectively be tested even when installed on a single VM.

• Temporary Remote Access to Customer’s Linux VM Environment:

  • Temporary Azure, AWS, or GCP accounts can be provided for load balancer and TLS configuration. Configure a Linux VM instance accessible via an SSH public key and provide the SSH public key (.pem file).

Summary of System Architecture for Production Use

The above system architecture is a summarized configuration diagram to aid user understanding, rather than a detailed system architecture.

The configuration above summarizes the key elements of the system architecture applied when using the actual QueryPie product. Users can access and use QueryPie through a web browser. Additionally, to connect to databases and systems from applications like DataGrip, MySQL Workbench, iTerm, and Putty running on user PCs, the QueryPie Agent can be installed on the PC.

The QueryPie server configured in the cloud features a redundant setup to function as a web application, and it is recommended to use MySQL and Redis provided as Managed Services by the cloud provider. The QueryPie Agent installed on a PC connects to the QueryPie server using a TCP-based proprietary protocol, and it is recommended to configure a Network Load Balancer for this purpose.