Integration glossary

The ideas behind connected systems, explained plainly.

Short explanations of the terms that come up when systems need to share data, each with a note on how STRAX handles it.

Passing on only what changed in a database, shortly after it changed, instead of copying whole tables on a schedule.

One agreed definition of shared records such as customer and order, which every connected system is mapped to once.

Keeping the same record current in several systems, so an edit made in any one of them reaches the rest.

Integration software that runs on your own servers, so the data moving between your systems stays under your control.

Integration delivered as a cloud service, where the vendor hosts the platform that connects your applications.

A central store that every connected system feeds and reads, so they share one current version of each record.

A service that offers a system's tools and data to AI assistants over an open protocol, within limits the system sets.

Marking a record deleted while keeping the row, and passing a delete on to the other systems that hold the same record.

A group of machines sharing one queue of work, so capacity grows by adding another machine to the pool.

A saved set of colours, fonts, logo and cover design that every report using it is rendered with.

Shared, versioned code that workflow code steps can call, kept in one place with its licences and the workflows that use it.

See it on your own systems.

A demo takes about an hour and shows these ideas working on systems like yours.

Request a demo → Request a quote