Skip to content

Trip-based Fuel Consumption Architecture

Trip-based Fuel Consumption Architecture

  • The Fleet service will send an SQS message to a new queue containing the trip details — assetId, deviceName, customer, apiKey, cycleId, startTimestamp, and endTimestamp.
  • A new Lambda service will be implemented to consume these SQS messages and perform the fuel-consumption processing for each completed trip.
  • Once calculated, the Lambda will update the corresponding cycle with the new fuel-consumption attribute(s).
  • To perform this processing, the Lambda service requires access to:
    • SQS
    • Sky Ledge API
    • S3 (skyledge-customer-data-backup and dagster-io-output buckets)
    • Fleet database (The flespi and flespi-mercury collections)

architecture.png