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
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")
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: