Journey Platform: A low-code tool for creating interactive user workflows

Journey Platform: Low-code notification workflow platform that allows technical and non-technical users to create complex workflows through…

Arjun Raman
10 min readbeginner
--
View Original

Overview

The Journey Platform is a low-code tool developed by Airbnb that enables users to create interactive user workflows for notifications. It empowers both technical and non-technical users to build personalized notifications efficiently, significantly reducing the time required for development.

What You'll Learn

1

How to create event-driven notification workflows using a drag and drop interface

2

Why using a Domain-specific language (DSL) enhances workflow flexibility

3

How to utilize the Action store to execute various tasks in workflows

4

When to implement dedicated lanes for different workflow categories to ensure SLA compliance

Prerequisites & Requirements

  • Understanding of event-driven architectures
  • Familiarity with Kafka for event handling(optional)

Key Questions Answered

How does the Journey Platform enable non-technical users to create workflows?
The Journey Platform provides a low-code interface that allows non-technical users to create workflows using a drag and drop functionality. This empowers users to build event-driven notification workflows without needing extensive programming knowledge, significantly reducing development time from 1-2 months to just 1-2 weeks.
What are the key components of the Journey Platform?
The Journey Platform consists of several key components including the Journey Platform UI, Workflow Orchestrator, and various stores such as Event Store, Action Store, and Attribute Store. These components work together to facilitate the creation and management of complex workflows.
What role does the Workflow Orchestrator play in the Journey Platform?
The Workflow Orchestrator is the core component that executes workflows by interpreting the DSL nodes. It manages state, interacts with the Action store, and listens for events from the Event store, allowing developers to focus on workflow logic rather than technical details.
How does the Journey Platform ensure SLA compliance for notifications?
The Journey Platform implements dedicated processing lanes for different workflow categories, allowing for prioritized handling of transactional notifications. This is achieved through event pre-processing and filtering, which reduces the load on the system and ensures timely delivery of critical notifications.

Key Statistics & Figures

Time reduction for supporting new use-cases
From 1-2 months to 1-2 weeks
This statistic highlights the efficiency gained through the Journey Platform's low-code capabilities.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Backend
Kafka
Used for event handling and triggering workflows.
Backend
Temporal
Utilized as the underlying workflow engine for state maintenance and orchestration.
Frontend
React Flow
Enables the visualization of workflows and provides interactive features like zooming and panning.

Key Actionable Insights

1
Utilize the drag and drop interface of the Journey Platform to quickly prototype notification workflows.
This approach allows teams to iterate rapidly on user engagement strategies without waiting for engineering resources, thus enhancing responsiveness to user needs.
2
Leverage the Action store to standardize common tasks across workflows.
By reusing actions, teams can maintain consistency in user communications and reduce redundancy in workflow design, leading to more efficient operations.
3
Implement event pre-processing to filter out unnecessary events before they reach the workflow handler.
This practice can significantly reduce the system's load and improve performance, ensuring that critical notifications are processed in a timely manner.

Common Pitfalls

1
Failing to filter events effectively can lead to system overload.
When all events are passed to the workflow handler without pre-filtering, it can overwhelm the system, causing delays in processing critical notifications. Implementing a robust filtering mechanism is essential to maintain performance.

Related Concepts

Event-driven Architecture
Low-code Development Platforms
Workflow Automation
Real-time Notifications