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

Guidance on database vs data warehousing #8

Open
tomkerkhove opened this issue Nov 14, 2017 · 0 comments
Open

Guidance on database vs data warehousing #8

tomkerkhove opened this issue Nov 14, 2017 · 0 comments

Comments

@tomkerkhove
Copy link
Contributor

For people whom are new to data analytics/processing it's sometimes hard to determine when a SQL database is good enough, if they need a data warehouse instead or need a mixture of both.

A scenario for this is where you have your API & backend processing using a database. Later on you need to provide reporting on a subset of that data. Do you run these on top of that database (pref. a replica for performance) or do you move that subset to a SQL data warehouse and run reports on top of that?

Interesting topics:

  • Impact on pricing and how this can be optimized
  • Design for this workload (Can be linked back to "Pipeline Orchestration, Control Flow and Data Movement")
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

1 participant