Data storage service recommendation (cost vs query latency) when using dataset with many time series

11 views
Skip to first unread message

Floris Calkoen

unread,
Oct 18, 2020, 4:07:07 PM10/18/20
to Google App Engine
I'm designing a small Flask Google App web-application/dashboard which will show some evolution patterns of climate data at global level. 

The observations were made at approx 1.5 million sites. Each site has approx 50 observations. Hence, the dataset consists around 1.5 million time series with in total 75 million rows.

Unfortunately we don't have a large budget for this app. However, we don't expect that many users (few per day). Nevertheless query latency should be kept as low as possible. 

What would be the optimal data storage service considering both query latency and costs? Should I just use Cloud Bigtable? Or maybe Cloud SQL? 


Reply all
Reply to author
Forward
0 new messages