When we designed the Onix intake for Ingram it was build to ingest publications to Ingram's tenant, and share them through the marketplace.

This is a really general overview of the content intake flow, from a content source (Bookwire, Ingram) sending

Here we present the information that we collect from the ONIX files that are sent to us for storage in Publica.la. We will indicate the type of data received, its relationship with the ONIX standard, the extractor responsible for obtaining such information, the required data, and the information that will be stored.

- https://ns.editeur.org/onix/en

To receive Onix intakes, we had to provide an SFTP server. On this SFTP server, is where the content source (Bookwire, Ingram) sends all the content that they provide. The problem is that they send GBs of data.

Medusa is the project that manages content intake automations for multiple tenants. It operates as a serverless application deployed on AWS Lambda using Laravel Vapor.

From wikipedia: