Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETL + Data warehouse #703

Open
lorenyu opened this issue Jul 24, 2024 · 2 comments
Open

ETL + Data warehouse #703

lorenyu opened this issue Jul 24, 2024 · 2 comments

Comments

@lorenyu
Copy link
Contributor

lorenyu commented Jul 24, 2024

No description provided.

@acouch
Copy link
Member

acouch commented Jul 29, 2024

Noting we are working on a data platform that includes Metabase as a BI tool and Postgres as a warehouse with a Python transformation service at grants.gov. For the BI tool we evaluatede a couple of options. Metabase might be a nice choice for the platform since Quicksight is so poor as an AWS option (Looker is much better on GC) and the fact it is open source makes it easy to spin up locally and could easily be adopted for new teams. Jypter notebooks might be a nice option for more dev-centered reporting needs. Apache Superset is also a high quality open source option that has a less user-friendly UI than Metabase but is pretty on par feature-wise.

We chose postgres over Redshift b/c the performance gains for Redshift don't appear to kick in until higher volumes of data than we are expecting in the near future. Postgres is also a known entity that is also easy to spin up locally. The whole toolchain is captured in a lightweight docker-compose file which is a nice outcome / productivity boost.

@coilysiren
Copy link
Contributor

I wrote both the ADRs listed above, so feel free to ask me for any more context as needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants