Pickup Taxi

This microservice’s job is to pick up data from different content repos (Connectors). Each connector implements an Adapter. Adapters understand how to manipulate data from the content repos, and the taxi uses the Adapter as middle man to request or execute commands to these Content Repos.

Responsibility 1: Requests the Local IDs from the Source Content Repos. Then the Taxi receives calls via REST from the adapter with the found Contents (and related Local IDs). The Local IDs are sent to the Content Diffuser using kafka messages, where a kafka message is produced for each content found in the Local IDs lookup.

Responsibility 2: To retrieve a Motation for a given Content. If Impulse doesn’t have Motations for any of the Contents or Dependencies, it means this is the first time we are analyzing this content, Impulse publishes a message for each missing Motation to the Pickup taxi so get the Raw Data from the Content Repo and Transform it into a Motation file. Then a kafka message with the generated Motation file is produced for the Content Diffuser to consume.

Responsibility 3: To request and return the Content Dependencies and System Objects from the Source Content Repo for a given content, the Content Diffuser only request dependencies and system objects for contents that need to be sync.