It looks like Chartbrew connects to various third-party tools directly, which can lead to silos/discrepancies in our experience.
It looks like Chartbrew connects to various third-party tools directly, which can lead to silos/discrepancies in our experience.
The only storage Chartbrew does is to cache the data while building a chart so the data source is not queried too many times and the user can see changes quicker. Afterwards, Chartbrew keeps the charts updated with data coming directly from the other tools.
Since this is the "best practice" architecture, we've made the decision to focus on integrations with data warehouses specifically— Snowflake, BigQuery, etc. I don't think Chartbrew has these.
Oftentimes data teams have those data sources in the warehouse already (or a process for ETLing new ones in).
Copying data only once means lower costs (maybe) and fewer inconsistencies.
Plus if they’ve done work to join/clean/transform the data in the warehouse they can take advantage of that for product analytics without having to reinvent the wheel in ChartBrew or Mixpanel.