MySQL integration

Connect application data across systems

MySQL tables and views can supply approved application records to Uplyst's intelligence layer. Stable source keys link orders, returns and stock movements with customers, payments and fulfilment information held elsewhere.

Scheduled reads suit periodic analysis and reference data. A supported binary log capture method can provide more frequent updates and deletion visibility. Source configuration, log format and the required freshness determine the approach; an initial snapshot and its change position need to cover the same starting point.

Transaction tracking for reliable recovery

With GTID mode enabled, MySQL assigns identifiers to transactions written to the binary log. Replicated transactions retain those identifiers across the replication topology, providing a reference for tracking execution and resuming processing. The business record still needs its own stable key, and downstream workflows need their own protection against repeated actions.

Keep orders and inventory consistent

Primary and composite keys identify the records affected by inserts, updates and deletes. Combined with the source database and table, these keys connect each change to the correct entity in Uplyst. Record history can retain the context of a deletion even after the record leaves the current view.

Character encoding, financial decimals and timestamp conventions affect comparisons across systems. Preserving their meaning keeps amounts, dates and customer identifiers consistent.