Data processing

Data processing is a core concept in the MatrixOne Intelligence product model. This page explains the problems it solves, its relationships with other objects, and its usage boundaries.

Definition

  • Data processing is primarily provided by workflows and the SQL editor.

  • A workflow uses nodes and dependencies to describe a repeatable processing flow; the saved DSL is the authoritative source for execution.

  • The SQL editor is suited to interactive queries; execution status, history, and plans are recorded in the monitoring system.

Object relationships

  1. Workflows read from connectors or Catalog and write results to Catalog or external targets.

  2. Compute resources run nodes, so resource status and concurrency configuration directly affect queue time.

  3. Execution records retain parameters, node states, logs, and artifacts for debugging, retries, and lineage analysis.

Design principles

  • Use least privilege and keep credentials in managed configuration.

  • Start by validating with minimal data or test objects, then expand the scope.

  • Version executable configuration and retain each run as an execution record.

  • Do not equate a visible entry with backend availability or resource authorization.

Note

These pages follow the current MOI 5.0 product model. If an entry is missing, check the workspace, permissions, and feature flags.

Operational guidance