APIs, queues, and legacy reality

Most enterprises run a braid of modern APIs, older databases, and human-maintained sheets. The goal is not purity—it is durable movement of data with traceability between systems.

Queues and idempotent workers tolerate retries and partial failures in ways that chained cron scripts cannot. Treat integrations as products: version them, log payloads, and alert on poison messages.

Where a full API does not exist yet, narrow adapters and scheduled exports can still be wrapped with the same monitoring and access controls as first-class services—so “temporary” does not mean invisible.