Hacker News Reader

Comment by leg100 | Hacker News Reader

Looks like there are two steps to this tool:

  1) Fetch data and put into a sql db
  2) Query sql db

Wouldn't it be better, performance aside, if there was just one step, i.e. querying the cloud with SQL, essentially an SQL-to-cloud-APIs interface. Otherwise you're always operating on out-of-date data.

View on HN

It's a cool idea for a feature!

The idea/advantage to have the data in regular SQL database - is to be able to work with all the standard tools and analytics dashboard you have and familiar with (AWS quicksight, Google DataStudio, sqlite shell, etc...)

The flipside is that performing joins in a process across many document databases (which is what this approach would resemble) is wildly non-performant compared to doing it in a relational database.

But now every time you run a query without a where clause you're firing API calls to all AWS services. And then maybe recursive API calls on top of that.

This is fine if you're a personal account, but then you wouldn't need this tool in the first place.

Reply on news.ycombinator.com