Ask HN: How did you scale your analytics workloads (Postgres)? Our product has some reporting features that require aggregations / analytics functionality.
Some of the analytics workloads are time series, others are not and we generally expect these analytics queries to resolve in ~2.5s We've recently decided to move these workloads to snowflake because we want to protect our transactional workloads. The snowflake devex has been pretty bad because we'd need a snowflake "instance" for each dev's postgres localhost, and we like that localhost postgres to be ephemeral. Additionally, it'd be nice to have this work all locally. One interesting piece of software I came across is DuckDB. It's lightweight. There's no additional storage needed. It's an interesting direction for me to test but I don't know if it'll satisfy our latency requirements. How have you separated and scaled out your analytics workloads from postgres? |