Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page

Was this helpful?

Understanding how Impulse diffs content

PreviousUnderstanding Impulse SyncNextUnderstanding Job Scheduling

Last updated 2 years ago

Was this helpful?

The following diagram explains the flow Impulse follows during a sync to recollect and process the required data to generate the reports and the data needed to diff content after the sync is done.

The diagram uses after the name of the service involved in each step the Rn format (example: Sync Manager (R1)) to denote the responsibility of the process in each step of the flow, the description of each service and responsibilities can be found under the section.

Download the full Flow Chart below

Services
285KB
diff-reports-flow.pdf
pdf
Complete Diff and report flow diagram
Diff and report flow part1
Diff and report flow part 2