Skip to main content

Introduction

What is a Journey Engine?

A Journey Engine is a lightweight, extensible microservice integration platform designed for seamless application configuration and integration with minimal coding. It allows users to integrate multiple services, modify existing integration flows, and deploy new ones without disrupting ongoing operations. The platform features an intuitive interface, making it easy for users with basic service knowledge to create integration flows effortlessly.

Why Choose the Journey Engine?

Key Functions:

  • Simplified Interface: Easily configure various services through integration flows.
  • Dynamic Node Deployment: Customize nodes within the flow setup.
  • Ready-to-Use Nodes: Instantly configure services using a comprehensive library of nodes.
  • Environment Configuration: Set up and configure deployment environments.
  • Variable Management: Define and manage environment and flow variables.
  • Flow Management: Validate, commit, and deploy created flows.
  • Version Control: Create and manage multiple versions of integration flows.
  • Gateway as a Service: Configure a service gateway to monitor and secure APIs.
  • Message Routing and Error Handling: Simplify message routing and optimize error management.
  • Migration Support: Facilitate smooth transition between server and flow environments.
  • User Management: Create personalized accounts and customize application roles for users.

Key Concepts and Terms:

Before utilizing the Journey Engine to construct your API calls, familiarize yourself with these key concepts and terms:

  • Journey Engine Canvas: The Canvas is a blank workspace where users can create, modify, and save flows. It serves as a platform for validating, committing, and deploying flows.
  • Flow: A Flow is a visual representation, similar to a flow chart, depicting an API call sequence. It comprises a series of events that execute specific actions. Users can create flows using default nodes available in the Journey Engine.
  • Nodes: Nodes are discrete components within a flow that perform specific actions. They are the building blocks of a flow and execute tasks defined by users.
  • Journeys: Journey is a platform for creating automated data workflows using APIs. It facilitates data movement between stages by configuring steps for data pulling, transformation via APIs, and pushing to other systems. The platform supports scheduling, monitors API calls, and manages errors effectively.
  • Flow Variable: A Flow Variable is a value accessible to all nodes within a specific flow. It simplifies flow design by centralizing frequently used values, eliminating r/edundancy.
  • Global Variable: A Global Variable is a value accessible to all nodes within a specific environment. It streamlines flow design by storing common values across all flows within that environment.
  • Folder: A Folder is a container that houses multiple flows. Each flow is stored as a file within the folder, facilitating organization and management.
  • Validate: Validation is the process of verifying the correctness of a flow. It checks flow data, type, and schema to ensure accuracy and consistency.
  • Commit: Committing involves finalizing the latest modifications made to a flow. Once committed, any subsequent changes are saved as new versions of the flow. Committing also locks the flow from further modifications.
  • Deploy: Deploy is the act of launching a flow service. A flow service is a functional service implemented using flows. Once deployed, the flow service becomes operational and ready to execute.