DX Graph:
Connect All Your Backends With an API-First Data Layer
Features and Capabilities
Connect to Any Source and Syndicate to Any Destination
In an enterprise stack, data needs to be syndicated across multiple backends including PIM, ERP, CRM, Commerce Engine, CMS, Search and more. Conscia offers various no-code approaches to moving data between systems including batch/file-based, real-time, event-driven and webhooks.
A Single Version of Truth for All Your Data
In order to get a comprehensive understanding of the data in various siloed systems and to create unified experiences, you need to connect and relate the data. Conscia offers a graph-based data layer that pulls in data from various systems, giving you a single version of truth of all the relevant data.
Prepare Your Data for Prime Time
One of the common challenges faced by organizations is the quality and heterogeneity of data residing in siloed systems. Before data is consumed by downstream applications, it is important to validate and optimize its quality. Conscia offers data quality checks to empower data providers and consumers to validate its quality before pushing to live environments.
Access Control and Governance
Conscia offers granular, collection and record-level control over data, allowing you to keep your data safe. Whether you're accessing data from the UI or the APIs, the controls carry through seamlessly.
Make Your Offline Data Accessible to Modern Frontends
Data in offline systems such as legacy CRMs and ERPs, databases, file systems, home grown applications is not readily available for online experiences. Conscia creates an data modernization layer on top of your existing backends, making it available to be accessed via real-time APIs.
Integration Patterns
Title | Source | Destination | Conscia Process | Example Scenario |
|---|---|---|---|---|
From external file system to Conscia Bucket | S3 Bucket, SFTP, or any other file system | Conscia Bucket | Conscia receives the file in the Bucket | Create a data extract from the ERP and push it to Conscia for further processing. |
Transform file in Conscia Bucket | File in Conscia Bucket | File in Conscia Bucket | File gets dropped to Conscia Bucket, Job processes file and outputs to another file in the Conscia buckets after some data transformation. | The extract from ERP needs to be transformed before it is pushed to an external webservice. You want to see the output of the transformation before you send it to an external system. |
Push data from file to external webservice endpoint. | File in Conscia Bucket | External Webservice Endpoint | Job processes file and writes to an external webservice endpoint. There is an ability to transform data on the way out. | Load product data directly into commerce engine, without first loading into the DX Graph for analysis and validation. |
Import data from file to DX Graph Collection | File in Conscia Bucket | DX Graph Collection | File gets dropped to Conscia Bucket, Job processes file and writes to a DX Graph. | Download data from PIM and load it into the DX Graph for further enrichment and validation. |
Export data from external webservice endpoint to a file | External Webservice Endpoint | File | Job pulls data from a webservice endpoint and writes to a file in a bucket. | Full product catalog download from PIM |
Import data from external webservice endpoint to DX Graph Collection | External Webservice Endpoint | DX Graph Collection | Job pulls data from a webservice endpoint and writes to DX Graph | Full product catalog download from PIM |
Export data from DX Graph to a File | DX Graph Collection | File | Job exports data from DX Graph Collection and Writes to a File. | Export invalid records from the DX Graph to a file so that the data owners can correct the issues in the source systems. |
Push data from DX Graph to external webservice endpoint. | DX Graph Collection | External Webservice Endpoint | Job pulls from DX Graph Collection and Writes to the Webservice Endpoint. | You want to validate the product information from the ERP before writing it to a downstream commerce engine or a search index. |
Update data in external application on a DX Graph Collection event | DX Graph Collection Event | Webservice Endpoint | DX Graph 'Record Updated Trigger' initiates a DX Engine Job Type, which can then write the record to an external system. | Update Search index if a product record gets updated in DX Graph |
Listen for updates from an external webhook | External Webhook | DX Engine Listener | External Webhook calls the DX Engine Listner which then processes the updated record. | The record is updated in the Commerce Engine. |
Update DX Graph Collection data via an API | DX Graph API | DX Graph | DX Graph API is called and the record within a DX Graph Collection is updated. | An External process such as an inventory service calls the DX Graph API with a CRUD operation. |
Update data in another system via an orchestration flow. | DX Engine | External Webservice Endpoint | The Orchestration Template in the DX Engine writes a record to an external endpoint. | Order record updated in commerce engine -> Webhook calls Conscia Listener -> Conscia DX Engine writes to OMS. |
