I’m looking for advice on technical strategies for user-facing analytics features (think real-time customizable dashboard). I’ve ended up in a situation where I want to design some analytics dashboards for end users that display aggregates/historical data for a number of years. The queries I want to run take way too long to run on-the-fly so I’ve resorted to pre-computing the data I care about...
Looking for some advice from more experienced engineers on here:I’ll preface this by saying I’m relatively new to the industry (couple years of experience) as an engineer. I’ve loved coding and working with cool tech since I was younger but I’ve only recently started working in a professional setting at a mid-size startup.I’m grateful that I have the opportunity to work on software full-time...
I have a solid understanding of the basics of relational DB performance (Indexing, explain analyze, different types of scans etc...) but I always seem to run into situations where I have complex and slow SQL queries and I'm not sure how to optimize them. I've often heard the rule of thumb that any user-facing query that takes longer than 100ms is too slow but I've never seen that play out in...