Skip to content

QIP Architecture

Jump to bottom
namu0421 edited this page Jul 17, 2025 · 2 revisions

The QIP architecture is built on a microservices model, where each component operates independently but collaborates via APIs to ensure seamless integration. Below is a detailed breakdown of its key elements:

Арх_в1

Core Microservices:

  1. Engine
    • Role: Executes predefined workflows ("chains") and manages their lifecycle.
    • Dependencies:
      • Uses Postgres for scheduling tasks and storing checkpoints (state-saving markers);
      • Communicates with the Run-Time Catalog to retrieve chain configurations.
    • Integration: Sends logs and sessions to Elastic for monitoring and analytics.
  2. Variables Management
    • Role: Manages dynamic variables across workflows.
    • Storage: Relies on Consul and Kubernetes (K8s) Secrets to store global variables.
  3. Sessions Management
    • Role: Works with sessions data.
    • Integration: Uses Elastic to log session activities and troubleshoot issues.
  4. Run-Time Catalog
    • Role: Enables users to create, configure, and deploy chains and services, prepares chains for execution by compiling dependencies and validating configurations.
    • Features:
      • Provides a UI for visual design of workflows;
      • Stores metadata in Postgres (chain definitions, snapshots, service integrations).
    • Process: Translates high-level designs into executable formats for the Engine.

Third Parties:

  • Consul
    • Data Storage: Maintains session details, logging levels, and shared variables critical for system operations.
  • Postgres
    • Use Cases:
      • Stores chain configurations, runtime states, and historical snapshots in the Catalog;
      • Manages scheduling logic and checkpoints for the Engine.
  • Elastic
    • Purpose: Centralized logging and monitoring tool for real-time insights into workflow performance and errors.

Scalability & Flexibility:

QIP’s modular design allows independent scaling of microservices based on demand (e.g., increasing Engine instances during peak loads). New functionalities, such as integrating monitoring systems, can be added without disrupting existing workflows.

Key Benefits:

  • Decentralized Governance: Each microservice acts autonomously, aligning technical architecture with organizational needs.
  • Fault Isolation: Issues in one service (e.g., Variables Management) do not affect others, ensuring system stability.

This architecture balances technical complexity with operational efficiency, making QIP adaptable for enterprise-scale integration tasks.

Clone this wiki locally