Capability map and product boundaries¶
Baseline: v4.2.5. MatrixOne is unified data infrastructure for AI agents and intelligent applications, built on SQL transactions/analytics with search, external-data and version-management interfaces.
Choose by task¶
Task |
Capability |
Boundary |
|---|---|---|
Business writes and analytics |
Transactions, JOIN/aggregation |
Actual isolation, errors, concurrency and shared capacity |
Semantic/keyword search |
Vectors, fulltext |
Embeddings, algorithm/flags, approximation and freshness |
Spatial analysis |
GIS types, functions |
SRID, units, precision and function scope, not implied spatial indexing |
Review data changes |
Git for Data, snapshots/branches/Diff/Pick/Merge |
Table scope, primary keys, permissions, conflicts and retention |
Files/lakehouse |
Stage/DATALINK, externals/Iceberg |
Ownership, credentials, writes, commit/file cleanup domains |
SQL inference |
Model, shape/dtype, native runtime/device |
|
Ingestion/tool integration |
CDC, drivers/connectors |
Source/sink direction, types, deletes, schemas and recovery |
Accounts/resources |
Multitenancy, Proxy/CN groups |
Data/permission isolation differs from physical resource isolation |
Status¶
Distinguish available SQL, default flags, experiments, external/native dependencies and validated production topologies. For HNSW, IVF-PQ, CAGRA and FULLTEXT2, check the corresponding experimental_* variables/build. A single Y does not establish every algorithm/device is enabled.
Selection and deployment¶
Use MatrixOne where one data interface should combine business facts, analytics, search and change workspaces. Validate SQL/drivers, types, workloads, faults and operations first. MySQL protocol access does not establish all SQL/binlog/connectors; see compatibility.
Local/private/public cloud are deployment choices. Design cross-cloud latency, log quorum, storage and residency separately. Performance/cost numbers need versions, hardware, data, workloads and controls rather than unlimited-scale, seamless-cross-cloud or 80%-reduction promises.
See the application developer guide. Source contributors have another path through contribution preparation.