Workflow Orchestration Embedded in your DevOps Tool Chain
summary
Claims that shifting workflow orchestration left speeds and stabilizes delivery by embedding scheduling in code using a Jobs-as-Code approach and a control-m backend. Shows a JSON-based control-m automation API hooked into Git and Jenkins, cites Gartner’s $200B and 75% in-house apps, Malwarebytes and amedeo's running hundreds of thousands of jobs per day and 5,000 developers with 5,000+ changes/month, and describes mission‑critical flows (90% of flights blocked if orchestration fails) — implementation runs at scale and prevents production surprises.
AI-written summary · about
chapters (5)
- 0:00Start
- 7:13Business Application Workflow Orchestration Challenge
- 14:09Pressure to deliver faster with higher qualit DevOps adoption helps to realize these benefits
- 17:23Traditional job definitions and workflow orchestration process
- 20:13Shift jobs left with Jobs-as-Code
related talks
30mBringing DevOps Success to Every App, Tool & Role in Your Org
21mOrchestrating multi-cloud data pipelines with
23mHow to Clean Up Your DevOps Dumping Ground
05mYou scream for microservices orchestration; I scream for batch...
41mContinuous Delivery Transformation: The New Way of Working
25mAI-Driven Workflow Orchestration at Enterprise Scale
05mDevOps over time
28mThe DevOps Pipeline