Destinations
Flowlyze supports two distinct modes for managing data destinations: active and passive, providing high flexibility in integration with external systems and in defining processing strategies.
There are two destination management modes:
- Active (push): Flowlyze sends data directly to the destination and guarantees delivery.
- Passive (pull): Flowlyze makes data available through a queue, and an external system retrieves it autonomously.
The choice between the two modes depends on integration needs and the responsibility you want to assign to each system.
Active Management
In active management, Flowlyze sends data directly to the configured destination and ensures correct delivery.
The system monitors each send, handles any retry attempts, and applies confirmation mechanisms to ensure the data actually reaches the target. In this mode, Flowlyze acts as a component responsible for transport reliability, reducing complexity for external systems.
Passive Management
In passive management, Flowlyze acts as a data producer and makes data available through a queue or similar mechanism. Messages are imported and kept waiting until an external system processes them autonomously, following a model similar to the publisher-subscriber pattern.
The system that consumes the data performs reads accompanied by an acknowledge, through which it notifies successful receipt to ensure reliable flow and correct message state management.
Connectors
📄️ HTTP
Flowlyze's HTTP destination allows sending data to external systems via HTTP requests, one for each message in the queue or one per message block. The request is built based on configured parameters (method, endpoint, headers, query string) while the body matches the JSON payload derived from the single record.
📄️ RDBMS (SQL)
The RDBMS destination allows Flowlyze to connect to any relational database accessible publicly via the Internet, without dependencies on a specific vendor. It is designed to implement data synchronization, migration, consolidation, or bidirectional integration scenarios between systems.
📄️ Flat file
The Flat File destination allows exporting a dataset to one or more files, according to logic completely decoupled from the file format, exactly as happens for the Flat File source.
📄️ Custom Adapter
Beyond standard connectors (source and destination), Flowlyze can be extended through external Apps called Custom Adapters.
📄️ Null
The Null destination is a dummy destination used when a real destination system is not necessary — or not yet available.
📄️ HTTP Message Queue
The HTTP Message Queue is a passive destination for retrieving messages from Flowlyze.
📄️ MongoDB
The MongoDB destination lets Flowlyze write documents to a MongoDB collection, complementing the MongoDB source (read). Use it for replication pipelines, syncing into document stores, and flows where the payload is already shaped as a JSON document.