#workflow #callback #events #data-processing #interaction #integration #querent

querent-synapse

A rust bridge capable of handling and executing querent workflows and be able to respond to incoming events via callbacks. Acting like a synapse between querent and the outside world.

26 stable releases

3.0.5 Apr 27, 2024
3.0.3 Apr 18, 2024
2.0.0 Mar 3, 2024
1.7.0 Mar 3, 2024
1.2.4 Dec 20, 2023

#10 in #interaction

Download history 124/week @ 2024-02-19 491/week @ 2024-02-26 142/week @ 2024-03-04 74/week @ 2024-03-11 78/week @ 2024-03-18 82/week @ 2024-04-01 142/week @ 2024-04-08 350/week @ 2024-04-15 287/week @ 2024-04-22 65/week @ 2024-04-29 2/week @ 2024-05-06 10/week @ 2024-05-13 25/week @ 2024-05-20 42/week @ 2024-05-27 83/week @ 2024-06-03

160 downloads per month

Apache-2.0 and LGPL-3.0-only

115KB
3K SLoC

Querent SDK for Rust

The Querent SDK for Rust facilitates seamless integration with Querent, an advanced asynchronous data processing engine, from Rust applications. This SDK streamlines the incorporation of Querent workflows, offering a straightforward approach to initiate, manage, and interact with Querent operations in Rust.

Features

  • Commence Querent workflows effortlessly from Rust applications.
  • Streamline interaction with Querent workflows, handling input and output data.
  • Trigger Querent events and callbacks directly from Rust.
  • Simplify the integration of Querent into Rust-based projects.

Installation

To utilize the Querent SDK for Rust, include it in your Cargo.toml:

[dependencies]
querent_synapse = "0.1.0"

Usage

Below is a basic example of starting a Querent workflow from a Rust application:

use querent_synapse::{Querent, WorkflowBuilder, Config, PyEventCallbackInterface, py_runtime_init};

fn main() {
    // Initialize the Python runtime
    py_runtime_init();

    // Create a Querent instance
    let mut querent = Querent::new();

    // Define the first workflow using the builder pattern
    let workflow1 = WorkflowBuilder::new("workflow_id_1")
        .name("My Workflow 1")
        .import("my_module")
        .attr("start_function")
        .add_argument(42)
        .config(Config::default())
        .event_callback(PyEventCallbackInterface::new())
        .build();

    // Define the second workflow
    let workflow2 = WorkflowBuilder::new("workflow_id_2")
        .name("My Workflow 2")
        .import("another_module")
        .attr("start_function")
        .add_argument("example_argument")
        .config(Config::default())
        .event_callback(PyEventCallbackInterface::new())
        .build();

    // Add workflows to Querent
    querent.add_workflow(workflow1).expect("Failed to add workflow 1");
    querent.add_workflow(workflow2).expect("Failed to add workflow 2");

    // Start workflows asynchronously
    querent.start_workflows().await.expect("Failed to start workflows");
}

Sequence Diagram:


sequenceDiagram
    participant Rust
    participant PythonGIL as "Python (with GIL)"
    participant Python
    
    Rust ->> PythonGIL: initialize_querent()
    PythonGIL ->> Python: 
    Rust ->> PythonGIL: add_workflow(workflow1)
    PythonGIL ->> Python: 
    Rust ->> PythonGIL: add_workflow(workflow2)
    PythonGIL ->> Python: 
    Rust ->> PythonGIL: start_workflows() (async)
    PythonGIL ->> Python: execute_workflow()
    Python ->> PythonGIL: handle_event()

Getting Help

If you encounter any issues or have questions regarding the use of the Querent SDK for Rust, please feel free to reach out on our community support channels.

License

The Querent SDK for Rust is provided under the Apache 2.0 License. See the LICENSE file for details.

Dependencies

~24–37MB
~579K SLoC