https://www.youngju.dev/blog 천천히 올바르게. AI Researcher & DevOps Engineer Youngju's tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering. ko fjvbn2003@gmail.com (Youngju Kim) fjvbn2003@gmail.com (Youngju Kim) Fri, 15 May 2026 00:00:00 GMT https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive.en https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive.en The AI-agent era has dragged workflow engines back into tier-1 infrastructure for every backend team. Temporal Cloud — founded by the people who built Uber Cadence — is the de facto standard, Inngest and Trigger.dev v3 are the TypeScript-first serverless contenders, Hatchet (YC W24) bets on Postgres as the only dependency, Restate ships a Rust core with Virtual Objects, and DBOS proposes Postgres-as-control-plane as an OS-level thesis. On the other side, the data-engineering camp — Airflow 3, Prefect 3, Dagster 1.10 — has settled into an asset-aware steady state, while Kubernetes-native Argo Workflows and the Netflix-born Conductor (now Orkes) own their own niches. Why this category came roaring back, what's actually the same and different, who to pick for AI agents vs payments vs ETL vs onboarding, and what Toss, Uber Eats Japan, LINE, and Mercari are running in production — a single map of where workflow engines stand in May 2026. Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) workflowdurable-executiontemporalinngesttrigger-devhatchetrestatedboscadenceairflowprefectdagsterargoconductor2026deep-diveenglish https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive.ja https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive.ja AIエージェント時代の到来でワークフローエンジンが再びtier-1インフラに戻ってきた。Uber Cadenceを作った人達が立ち上げたTemporal Cloudが事実上の標準、TypeScriptファーストのInngestとTrigger.dev v3、Y Combinator W24出身でPostgres頼みのHatchet、RustコアでVirtual ObjectsのRestate、Postgresをcontrol planeにするDBOSのOS-as-a-databaseという論。一方でデータエンジニアリング陣営のAirflow 3・Prefect 3・Dagster 1.10はasset-aware steady stateに落ち着き、k8sネイティブのArgo WorkflowsとNetflix発のConductor(Orkes)もそれぞれの定位を固めた。なぜこのカテゴリが再び注目されたのか、何が同じで何が違うのか、AIエージェント・決済・ETL・オンボーディングという代表的ワークロードでそれぞれ何を選ぶべきか、そして韓国のトス、Uber Eats Japan、LINE、メルカリは実際何をproductionで動かしているのか — 2026年5月時点のワークフローエンジン地図を一度に描く。 Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) workflowdurable-executiontemporalinngesttrigger-devhatchetrestatedboscadenceairflowprefectdagsterargoconductor2026deep-dive日本語 https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive https://www.youngju.dev/blog/culture/2026-05-15-workflow-engines-2026-temporal-inngest-trigger-hatchet-restate-dbos-airflow-deep-dive AI 에이전트 시대가 열리며 워크플로우 엔진이 다시 1군 인프라가 됐다. Temporal Cloud는 Uber Cadence를 만든 사람들이 세운 표준, Inngest와 Trigger.dev v3는 TypeScript 친화 서버리스, Hatchet은 Y Combinator W24 출신의 Postgres 기반 신예, Restate는 Rust 코어와 Virtual Objects, DBOS는 Postgres를 control plane으로 삼는 OS-as-a-database 논제. 한쪽에서는 데이터 엔지니어링의 Airflow 3·Prefect 3·Dagster 1.10이 자산 중심 모델로 재편됐고, k8s 진영의 Argo Workflows와 Netflix가 Orkes에 넘긴 Conductor가 자기 자리를 굳혔다. 왜 다시 중요해졌나, 무엇이 같고 무엇이 다른가, AI 에이전트·결제·ETL·온보딩 중 어떤 워크로드에 누구를 골라야 하나, 그리고 토스·우버 이츠 재팬·LINE·Mercari는 무엇을 쓰고 있나 — 2026년 5월의 좌표를 한 번에 그려본다. Fri, 15 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) workflowdurable-executiontemporalinngesttrigger-devhatchetrestatedboscadenceairflowprefectdagsterargoconductor2026deep-dive https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive.en https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive.en The 2026 landscape of scheduled tasks. Classic cron is still alive, and systemd timers became the modern Linux replacement. Cloud-side: Vercel Cron, AWS EventBridge Scheduler (replaced CloudWatch Events Rules in Nov 2022), Cloudflare Workers Cron Triggers, GitHub Actions schedule, GitLab schedule pipelines. Distributed queues: BullMQ (Node), Sidekiq (Ruby), Celery Beat / RQ / dramatiq / APScheduler (Python), Quartz / Spring @Scheduled (Java), Hangfire (.NET). Workflow side: Airflow / Dagster / Prefect / Temporal Schedules / Inngest Crons / Trigger.dev v3 / Hatchet. Containers: k8s CronJobs and Nomad periodic jobs. Monitoring: Healthchecks.io / Cronitor.io. With Korean and Japanese case studies. Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) cronscheduled-taskssystemd-timersvercel-cronaws-eventbridge-schedulercloudwatch-eventscloudflare-workers-crongithub-actions-schedulegitlab-schedulek8s-cronjobsbullmqsidekiqcelery-beatrqdramatiqapschedulerairflowdagsterprefecttemporal-schedulesinngest-cronstrigger-dev-v3hatchetquartzspring-scheduledhangfirefcronanacronhealthchecks-iocronitor-io2026deep-diveenglish https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive.ja https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive.ja 2026 年のスケジュールタスク地形図。古典的な cron は今も健在で、systemd timers が Linux のモダンな代替となった。クラウド側には Vercel Cron、AWS EventBridge Scheduler（2022 年 11 月に CloudWatch Events Rules を置き換え）、Cloudflare Workers Cron Triggers、GitHub Actions schedule、GitLab schedule pipelines が並ぶ。分散キューは BullMQ（Node）、Sidekiq（Ruby）、Celery Beat・RQ・dramatiq・APScheduler（Python）、Quartz・Spring @Scheduled（Java）、Hangfire（.NET）。ワークフロー側は Airflow・Dagster・Prefect・Temporal Schedules・Inngest Crons・Trigger.dev v3・Hatchet。コンテナは k8s CronJobs と Nomad periodic jobs。監視は Healthchecks.io / Cronitor.io。韓国・日本の事例まで一気にまとめる。 Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) cronscheduled-taskssystemd-timersvercel-cronaws-eventbridge-schedulercloudwatch-eventscloudflare-workers-crongithub-actions-schedulegitlab-schedulek8s-cronjobsbullmqsidekiqcelery-beatrqdramatiqapschedulerairflowdagsterprefecttemporal-schedulesinngest-cronstrigger-dev-v3hatchetquartzspring-scheduledhangfirefcronanacronhealthchecks-iocronitor-io2026deep-dive日本語 https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive https://www.youngju.dev/blog/culture/2026-05-16-cron-scheduled-tasks-2026-systemd-timers-vercel-cron-aws-eventbridge-scheduler-k8s-cronjobs-bullmq-sidekiq-temporal-deep-dive 2026년 스케줄된 작업의 지형도. 클래식 cron은 여전히 살아있고, systemd timers가 Linux의 모던 대체가 됐다. 클라우드 쪽은 Vercel Cron, AWS EventBridge Scheduler(2022.11에 CloudWatch Events Rules 대체), Cloudflare Workers Cron Triggers, GitHub Actions schedule, GitLab schedule pipelines가 채운다. 분산 큐는 BullMQ(Node), Sidekiq(Ruby), Celery Beat·RQ·dramatiq·APScheduler(Python), Quartz·Spring @Scheduled(Java), Hangfire(.NET). 워크플로 쪽은 Airflow·Dagster·Prefect·Temporal Schedules·Inngest Crons·Trigger.dev v3·Hatchet. 컨테이너 쪽은 k8s CronJobs와 Nomad periodic jobs. 모니터링은 Healthchecks.io / Cronitor.io. 한국·일본 사례까지 한 번에 정리한다. Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) cronscheduled-taskssystemd-timersvercel-cronaws-eventbridge-schedulercloudwatch-eventscloudflare-workers-crongithub-actions-schedulegitlab-schedulek8s-cronjobsbullmqsidekiqcelery-beatrqdramatiqapschedulerairflowdagsterprefecttemporal-schedulesinngest-cronstrigger-dev-v3hatchetquartzspring-scheduledhangfirefcronanacronhealthchecks-iocronitor-io2026deep-dive https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive.en https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive.en The 2026 landscape of durable execution. Temporal Cloud has become the de-facto workflow standard, Restate is challenging it with a simpler RPC model. Hatchet, Inngest, and Trigger.dev v3 are the developer-first lightweight options; DBOS persists program state on Postgres; Dapr Workflows owns the Kubernetes-native side. We cover AWS Step Functions, GCP Workflows, Azure Durable Functions, Cadence, Conductor, Zeebe, the Saga/Outbox/idempotency patterns, AI agent orchestration, and Korean and Japanese big-tech case studies — all in one place. Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) durable-executionworkflow-enginestemporalrestatehatchetinngesttrigger-devcadencedbosdapr-workflows2026deep-diveenglish https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive.ja https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive.ja 2026年の耐久実行(durable execution)の地形。Temporal Cloud はワークフローの事実上の標準となり、Restate はよりシンプルな RPC モデルで挑戦中。Hatchet/Inngest/Trigger.dev v3 は開発者ファーストの軽量選択肢、DBOS は Postgres 上にプログラム状態を永続化し、Dapr Workflows は Kubernetes ネイティブの地位を確立した。AWS Step Functions・GCP Workflows・Azure Durable Functions・Cadence・Conductor・Zeebe まで、Saga/Outbox/冪等性パターン、AI エージェントのオーケストレーション、韓国・日本の大手 IT 採用事例を一気に整理する。 Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) durable-executionworkflow-enginestemporalrestatehatchetinngesttrigger-devcadencedbosdapr-workflows2026deep-dive日本語 https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive https://www.youngju.dev/blog/culture/2026-05-16-durable-workflow-engines-2026-temporal-restate-hatchet-inngest-trigger-dev-cadence-dapr-orchestra-deep-dive 2026년 내구성 실행(durable execution) 지형도. Temporal Cloud는 워크플로우 표준이 되었고, Restate는 더 단순한 RPC 모델로 도전한다. Hatchet/Inngest/Trigger.dev v3는 개발자 우선 라이트웨이트 옵션, DBOS는 Postgres 위에 프로그램 상태를 영속화하고, Dapr Workflows는 쿠버네티스 네이티브로 자리 잡았다. AWS Step Functions·GCP Workflows·Azure Durable Functions·Cadence·Conductor·Zeebe까지, Saga·Outbox·Idempotency 패턴, AI 에이전트 오케스트레이션, 한국·일본 빅테크 실사용 사례를 한 번에 정리한다. Sat, 16 May 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) durable-executionworkflow-enginestemporalrestatehatchetinngesttrigger-devcadencedbosdapr-workflows2026deep-dive