Data workflow
This page showcases the workflow by which projects get their data

This happens when someone clicks on the "Refresh data" link in the subscription interface in the back-office. It contacts datastream API to ask for the queue to be filled with data. This step is optional because it's caused by manual intervention through the project's back-office which happens mostly during development/review. In production data is pushed automatically in the queue once available by other part of the Michelin org (i.e Lizeo).
Once the queue is ready and filled with data, datastream contacts the project thanks to the information contained in the consumer document in the database.
The project contacts the queue thanks to the information it has in its configuration (URLs, token, ...).
Last updated
Was this helpful?