Dropoff Taxi

This microservice’s primarily job is to receive objects for delivery from the Content Diffuser and to deliver those contents to the different destination content repos (Connectors). Each connector implements an Adapter. Adapters understand how to manipulate data from/to 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 Destination 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 sync given elements to the Destination Content Repos. The elements given by the Content Diffuser for syncing to the Content Repos endpoints can be Motation Objects, Content Dependencies, System Objects and the main content itself.

The elements to deliver are always given to the Adapter as Raw Data, and the adapter uses the Raw Data to Sync the given data into the Content Repo.

Most of the elements to sync are given to the taxi from the Content Diffuser as Motations, when the received object is a Motation the taxi request to the Transformer to transform that Motation to Raw Data and sends the Raw Data to the adapter for syncing.