Winston Lin.
All small builds

oci-fn-queue-worker-starter

Starter pattern for queue-driven OCI Functions work that makes the handoff, retry edge, and worker boundary easier to inspect.

Functions patternView on GitHub

What it does

The first useful run is a worker result that already shows task identity, status, and whether the item is retryable. That makes the starter repo useful before you add a real queue trigger, dead-letter handling, or metrics layer.

Try it locally

python3 - <<'PY'
import json
from func import handle_work_item
payload = json.load(open('sample-work-item.json'))
print(json.dumps(handle_work_item(payload), indent=2))
PY

Example output

{
  "ok": true,
  "task_id": "task-1042",
  "worker": "invoice-sync",
  "status": "processed",
  "processed_records": 3,
  "retryable": false
}

Where it helps

Use this when a starter pattern should make the queue handoff and worker result contract obvious before the rest of the background-processing workflow is built out.