Skip to content

Instantly share code, notes, and snippets.

@judell

judell/cody-steampipe-02.md

Created May 27, 2023 19:13
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save judell/e3ef0f3daaf9e2fc8cd9d44f5e89ae51 to your computer and use it in GitHub Desktop.
Save judell/e3ef0f3daaf9e2fc8cd9d44f5e89ae51 to your computer and use it in GitHub Desktop.
Download ZIP
cody-steampipe-02
Raw
cody-steampipe-02.md

Me

"The dashboard server executes each SQL query and caches the results."

That's wrong. The Steampipe CLI runs the query and passes results to the dashboard server

Cody

Read 12 files You're right, my previous statement was incorrect. The correct explanation is:

The Steampipe CLI executes each SQL query and passes the results to the dashboard server. The dashboard server then renders the results in the UI. It does not cache the query results itself.

When a user refreshes data or changes an input in the UI, the dashboard server re-runs the necessary queries by sending them to the Steampipe CLI to get updated data and re-render the UI.

So the flow is:

User runs a query or loads a dashboard in the UI

The dashboard server constructs the SQL query and sends it to the Steampipe CLI

Steampipe CLI executes the query and returns the results to the dashboard server

The dashboard server renders the results in the UI

User refreshes data or changes input

Dashboard server re-runs queries by sending to Steampipe CLI

Steampipe CLI executes queries and returns updated results

Dashboard server re-renders UI with updated data

The dashboard server acts as a frontend interface, executing queries through the Steampipe CLI and handling the UI rendering of results. The Steampipe CLI acts as a database backend, executing the queries and returning data to the dashboard server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment