Skip to the content.

Component relationships

Package and host boundaries, not separate microservices. The SQS edge abbreviates queue delivery (expanded in deployment). No Media Library-to-media-player dependency was established. Admin page state uses Vue refs/computed and useAdminSession; no dedicated Pinia media store is evidenced. UI components include AdminMediaTile, AdminMediaDrawer, AdminMediaVariants and AdminMediaMessages.

Legend: all drawn relationships are source-verified; branches are conditional execution paths. No inferred service is drawn.

flowchart TB
  UI["«component» Admin media page and drawer"]
  C["«component» media-client"]
  A["«component» Admin media routes and media-service"]
  N["«component» media-nuxt routes in web"]
  L["«component» media / MediaLibrary"]
  S["«adapter» SQLite and filesystem"]
  W["«adapter» media-aws / DynamoDB and S3"]
  Q["«component» SQS worker"]
  I["«component» image / sharp transform"]
  P["«component» Web media-player demo"]
  MP["«component» media-player / TgmcPlayer"]
  UI -->|HTTP through createMediaApiClient| C
  C -->|Bearer JSON requests| A
  A -->|local mode calls| L
  A -->|MEDIA_API_URL forwarding| N
  N -->|getMediaLibrary| L
  L -->|local factory injects ports| S
  L -->|AWS factory injects ports| W
  N -->|optional SQS jobId dispatch| Q
  Q -->|runMaterializeJob| L
  L -->|ImageTransformer| I
  P -->|imports| MP

Source evidence