Core concept

Liteflow is based on the concept of workflows.

An application is based on one or multiple workflows that describe a specific feature in an application.

Workflows are event-based, meaning that the steps that this workflow triggers are based on an event from a specific service.

Workflows let you connect multiple services and execute a series of tasks when an event occurs.

Example: A workflow that listens for an event of Service A and triggers Service B and Service C only when some data match specific criteria.

Workflows are nondeterministic finite state machines that perform state transition when matching events occur but don't support the cycle.

A workflow is a list of steps that describes a specific business logic.

A step can be one of the following:

The first step of a workflow is the only step which must be an event trigger.

Workflows can be graphically represented as a UML activity diagram with actions and conditions but without cycles and concurrency. Graphic representation is an excellent first step to conceptualize an application before implementing it.