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.
Change data capture (CDC)
Passing on only what changed in a database, shortly after it changed, instead of copying whole tables on a schedule.
Read the definition →Canonical data model
One agreed definition of shared records such as customer and order, which every connected system is mapped to once.
Read the definition →Two-way data synchronisation
Keeping the same record current in several systems, so an edit made in any one of them reaches the rest.
Read the definition →Self-hosted integration platform
Integration software that runs on your own servers, so the data moving between your systems stays under your control.
Read the definition →iPaaS (integration platform as a service)
Integration delivered as a cloud service, where the vendor hosts the platform that connects your applications.
Read the definition →Data hub
A central store that every connected system feeds and reads, so they share one current version of each record.
Read the definition →See it on your own systems.
A demo takes about an hour and shows these ideas working on systems like yours.