You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently end users have to manually generate csv files for different events going in a program and ingest them in cqube. There is a scope of automation here if we can capture change events in database and generate the program, event files directly using a config file.
Solution Archtiecture
We are using Estuary as a CDC provider here. A data pipeline is created which sends every event on the database to a webhook. The webhook accepts the data, parses it, generates related CSV files, and stores it in a S3-like storage (for POC we are storing on the local system only). A cron job is running which ingests data into CQUBE after some interval of time that is configured.
The ingest files generated are structured as follows:
Date
ProgramName
EventName
This POC is backward compatible as well - we can add it to the already existing c-qube deployments with ease.
The text was updated successfully, but these errors were encountered:
Problem statement
Currently end users have to manually generate
csv
files for different events going in a program and ingest them incqube
. There is a scope of automation here if we can capture change events in database and generate the program, event files directly using aconfig
file.Solution Archtiecture
We are using Estuary as a CDC provider here. A data pipeline is created which sends every event on the database to a webhook. The webhook accepts the data, parses it, generates related CSV files, and stores it in a S3-like storage (for POC we are storing on the local system only). A cron job is running which ingests data into CQUBE after some interval of time that is configured.
The ingest files generated are structured as follows:
This POC is backward compatible as well - we can add it to the already existing c-qube deployments with ease.
The text was updated successfully, but these errors were encountered: