Airflow schedules tasks that depend on each other. That is the whole product.
When it is the right answer
You have jobs that must run in order, on a schedule, with retries when one fails, and you want to see the history of those runs in one place. If you are doing that with cron and a shell script that emails you, Airflow is worth the operational cost.
When it is the wrong answer
- You have one job that runs once a night. Use cron.
- You need sub-second latency between steps. Use a queue.
- You do not have anyone who wants to own a scheduler. It will rot.
The operational cost nobody mentions
Airflow needs a database, a scheduler process, a webserver, and somewhere to keep logs. On a single small server that is fine. When it breaks, it breaks in the scheduler, which is the part nobody watches.
Reference material
Where a review discusses a published standard or a vendor API, we work from the primary document rather than a secondary summary. For storefront data that means the vendor’s own Admin API reference; for real-time transport questions it means the governing specification, for example RFC 3550. If a document we cite has been superseded, tell us and we will correct the link.
How to read this page
“If a claim about a connector cannot be checked against the vendor’s own documentation, it belongs in a blog post, not in a review.” — our internal editing rule.
Everything on this page is written to be checkable. Where we cite a vendor’s API or a published standard, the link points at the primary document rather than a summary, so a reader can verify the claim without taking our word for it.
What is on this page
This page is reference material for Rocon Software Review: roughly 300 words of context, 2 primary-source links, and the specific limits of what we can tell you here.
Scope
The scope is deliberately narrow. It covers what the page title says and nothing adjacent, because a reference page that sprawls is a page nobody finishes. Three constraints apply: the material is checked at publication, re-checked quarterly, and corrected in place with a dated note when it goes stale.
How it is maintained
Two people maintain this page. Reviews are re-checked every 90 days against the vendor’s published pricing, and every correction is dated in the page body rather than silently applied.
Terms used on this page
A connector is a service that moves records between two systems on a schedule or on an event. A webhook is an HTTP callback that a system sends when something changes, rather than waiting to be polled. An item fulfilment is the record that says a physical shipment left the warehouse, and it is a different object from the sales order it belongs to.
- Sales order — the record of what a customer bought
- Item fulfilment — the record of what actually shipped
- Inventory level — available quantity at a specific location
- Location — a warehouse, a store, or a virtual bucket
- Matrix item — a product with variants inherited from an option schema
- Upsert — create if absent, update if present
- Idempotency key — a value that stops a retry from creating a duplicate
- Reconciliation — the manual or scripted comparison of two ledgers
- Backfill — replaying historical records into a new system
- Cutover — the moment the new system becomes authoritative
- Drift — the state where two systems disagree without either raising an error
- Circuit breaker — a mechanism that stops retrying a failing integration