Temporal Architecture for Mimir & Ardome

☁️ CLOUD

🅼 Mimir

(Cloud MAM)

☁️ Mimir Worker

✓ Search / Get Asset
✓ Metadata
✓ Create / Update
✓ Export / Jobs
✓ Status via API / Webhooks

⬌
HTTPS
API

⚙️ Temporal

⚙️ Workflow Engine

Orchestration
State Management
Retries / Timeouts
Durable Execution

📊 Visibility & UI

Real-time Progress
History & Logs
Alerts & Notifications
Operator Actions

📋 Task Queues

mimir-tasks
transfer-tasks
ardome-tasks
other-tasks

🏢 TV STATION (ON-PREM)

🔧 Ardome (On-Prem MAM)

👷 Ardome Worker (On-Prem)

✓ Search / Get Asset
✓ Register / Ingest
✓ Metadata
✓ Job Status
✓ Events / Webhooks

🚚 Transfer Worker (On-Prem)

✓ Receive from Cloud
✓ Move / Validate
✓ Deliver to Ardome

📁 Shared Storage /
File System

👤 Operator / User

Start Workflows • Monitor Progress • Take Actions

🔒 Firewall Note: Typically only outbound 443 (TLS) allowed
Worker initiates connection to Temporal (no inbound needed)

📋 EXAMPLE WORKFLOW

START

EXAMPLE
WORKFLOW

Find Asset in Mimir

Search and get
asset details

🔍

Transfer to Station

Transfer media
to on-prem
storage

☁️ → 🏢

Register in Ardome

Create / register
asset in Ardome

🔧

Wait for Processing

Wait for ingest,
QC, transcoding,
etc.

⚙️

Ready

Asset is ready
for use

✅

✅ WHY THIS WORKS WELL

Temporal handles orchestration, state, retries, and visibility
Workers integrate with each system using their APIs
On-prem worker connects outbound to Temporal (no inbound needed)
Scales to multiple stations and systems
Operators get full visibility and control

⚠️ POSSIBLE BLOCKERS / CONSIDERATIONS

🔒 Firewall / Network

Outbound connection from station to Temporal must be allowed (usually TLS 443). Strict policies may need approval.

💻 Software Versions

Older versions of Mimir, Ardome, or other systems may have limited or no usable APIs.

👁️ Visibility / Status

Systems must expose their status via API, webhook, event, logs, etc. If not, workers cannot know the true progress reliably.

Temporal Architecture for Mimir (Cloud) and Ardome (On-Prem)