And you are here why?

(For when you need to get beyond basic container orchestration) Seriously, Kubernetes is great for your baseline orchestration — stuff like scheduling, nodes, volumes, and so forth. It’s when you get into the complexity of workflows — like all the entertainment around continuous delivery — that you eventually realize that you need   something more , and that your increasingly complex python/scripting setup needs to be cleaned up. Enter Argo —  https://github.com/argoproj/argo  — which takes care of specifying, scheduling, and co-ordinating these workflows, the steps therein, and the interactions between these steps, all in a simple declarative style (YAML! You can munge this into your repo, and be well on your way towards immutable infrastructure!) In addition, Argo also integrates artifact management — which, in and as of itself, is ridiculously useful. My highly unscientific survey guesstimates that around 70% of the cruft in most existing home-built systems revolves ar...

WaaS is basically what Amazon has just released with their Amazon Simple Workflow (SWF) .  From the blog post This new service gives you the ability to build and run distributed, fault-tolerant applications that span multiple systems (cloud-based, on-premise, or both). Amazon Simple Workflow coordinates the flow of synchronous or asynchronous tasks (logical application steps) so that you can focus on your business and your application instead of having to worry about the infrastructure Picture a business process which consists of a bunch of individual tasks that need to be done in some specific sequence based on various inputs.  e.g.,   When an order comes in , check to see if we have inventory.  If we do, fill the order. If we don't, put the order in the "back-ordered" pile. Each of these tasks is called an Action .  A given Action is performed by a Worker . The whole business process is called a Workflow .  And the thingy doing all the d...