Since the regularly scheduled date of May 1st happens to be a holiday in Singapore, we’ll be skipping the next session.
Please join us when we return on 2025-06-05T15:00:00Z to talk about how to define executable workflow diagrams using JSON. We’ll cover various workflow mechanisms like forks, buffers, joins, listeners, and streams, and demonstrate how to incorporate these mechanisms into a workflow diagram.
We’ll also talk about reusable workflow “sections” which allow you to encapsulate portions of a workflow into a reusable unit, selectively exposing specific input slots, output signals, and buffers of your section that can be connect with other elements in your workflow. “Sections” allow you to apply good software engineering practices to your workflow design by defining an API (the set of inputs, outputs, and buffers that your section exposes) and plugging the section into any workflow where it may be useful. Complex workflows can be simplified by breaking them down into sections, and the responsibility of designing each section can be delegated across multiple team members or even across different teams. Sections can also be used inside of other sections, allowing multiple layers of abstraction.