QuerySurge Architecture and Architecture Diagram

Versions: 8.0+

The QuerySurge Core Architecture

QuerySurge is a Web 2.0 application, with, as is typical, an App Server and Database. Users access QuerySurge through a supported browser. QuerySurge also requires deployment of one or more QuerySurge Agents.

The QuerySurge Agent

The Agent is the QuerySurge component that actually executes queries against Source and Target and returns the results to QuerySurge. Agents are deployed in a hub-and-spoke relationship to the QuerySurge App Server, with the App Server at the hub and the Agents on the spokes. The idea of the Agent is simple: more Agents equals more simultaneously running queries. 

The QuerySurge Stats Monitor

This is a standard component that lets QuerySurge monitor the resource consumption. It can alert you, for example, if threshold disk usage levels are exceeded.

The QuerySurge DevOps and RESTful APIs

These optional QuerySurge components may be deployed in your environment to give external processes access to execute QuerySurge. Common use cases are to drive QuerySurge from a Scheduler (e.g. commercial scheduler, Windows Scheduler, Linux cron job), from a Continuous Integration (CI) build process, or from an ETL tool.

QuerySurge Test Management Tool Connectors

This optional QuerySurge component lets you integrate QuerySurge with your Test Management tools. Currently, HP QC/ALM, Microsoft TFS and IBM RQM are supported. With the QuerySurge connectors, you can execute QuerySurge from your Test Management tool and see the Pass/Fail results from QuerySurge tests in your tool. You'll also see QuerySurge links in your tool for each test back to the underlying data, so you can easily see the data behind each Passing or Failing test.