mfateev

12 ms·

91.
by mfateev 7y ago
Cadence doesn't require workflow and activity type registrations which eliminates most of the problems with SWF versioning. Cadence supports versioning of the workflow code out of the box. Any change has to be protected with a version
92.
by mfateev 7y ago
Cadence is a service. The workflow and activity code lives outside of it. Think about Cadence workflow and activity code the same way you think about a queue consumer which is external to the queueing service.
93.
by mfateev 7y ago
Argo workflows are DAGs written in YAML. The types of workfows you can create using this syntax is very limited. Cadence gives you full power of a programming language like Java or Go to implement workflow logic. It is possible to implement
94.
by mfateev 7y ago
The main difference is that workflow has state and tasks can be very long running. Also workflow can react to external asynchronous events. Visibility into overall progress is also a very important feature. When using a queueing system it i
95.
by mfateev 7y ago
I'm from Cadence team, so I'm obviously biased :). Besides very different implementation backends the main difference is that Conductor defines workflows through a JSON based DSL and Cadence defines workflows as code. Because of t
96.
by mfateev 7y ago
Besides the UI Cadence provides a CLI that supports most of the API features. The core API is almost the same, so porting an existing python client should not be a very large task.
97.
by mfateev 7y ago
Cadence vs SWF Cadence was conceived and is still led by the original tech leads of the SWF. SWF had no new features added for the last 5 years. Cadence is open sourced and is under active development. Cadence was initially based on SWF pub
98.
by mfateev 7y ago
It can be used for them. There are multiple customers that have workflows with both synchronous and asynchronous components. For example customer sign up flow might require a long running background check.
99.
by mfateev 7y ago
My personal opinion is that the workflow is any business logic that goes beyond a single request reply. Examples of workflows: * Service deployment. * Uber trip * Media processing (download file, transcode, upload result) * Order processing
100.
by mfateev 7y ago
For example the Uber loyalty program needs to accumulate points (similar to airline points). A customer workflow receives trip completion events and updates the state accordingly. When a certain number of points is reached some actions (mos
101.
by mfateev 7y ago
Cadence allows to write workflows as code. Think of it as a virtual machine for OO code that makes that code fully fault tolerant to process failures. As it is code it can be used to implement any business logic. Camunda is BPMN engine whi
102.
by mfateev 7y ago
We have both very low scale use cases as a single distributed cron as well as very high scale use cases in production at Uber.
103.
by mfateev 7y ago
AFAIK Netflix Conductor was inspired by the AWS Simple Workflow engine. The Cadence is a direct evolution of SWF in the open source world. I was tech lead for both of them :).
104.
by mfateev 7y ago
Cadence does support processes that run unlimited time. We have workflows in production that are always running. For example there are services at Uber that have an always open Cadence workflow per rider.
105.
by mfateev 7y ago
Cadence supports both long-runnig as well as very short tasks.
106.
by mfateev 7y ago
The biggest difference besides the programming model is scale. Luigi and Airflow target data pipelines that don't require much scale. Cadence is built to support business level transactions. It can handle tens of thousands of events pe