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?

  1. Services

Job Depot

The Job Depot stores all possible Sync jobs. Currently, in Impulse Jobs need to be defined before they can be used. A Job example would be providing a number of Sources and a Number of Destinations. The Job can be Manual or Automatic as described under the terms. In addition to this, each Source/Destination has its own detail (JSON) which the Taxis will use to figure out what to get. The detail can and must likely be different for each Content Repo as it is specific to interact with the Content Repo’s APIs. This is how Impulse deals with Folders being different or queries and content being different between systems.

Responsibility 1: The job detail is responsible for storing the Job and populating to pass along any requested Job through the Sync Process.

PreviousMotator Binary DepotNextEndpoint Depot

Last updated 2 years ago

Was this helpful?