Redash Reviews

GraphQL Cache Reviews

Redash mentions (19)

• Tool or service for querying and exposing database through API

  I am looking for service or tool similiar to Metabase or Redash that allows me to add data source - for example Postgres connection, and create raw SQL queries that can be shared or exposed through API. So instead of keeping raw SQL code somewhere, my other service would call this tool e.g. http://microservice/query=1?param1=xx&page=2 and get the results from the DB. These calls are internal only and part of ETL... Source: about 3 years ago

• Did anyone try Openblocks for multi-tenant client reporting?

  I have tried Metabase, Redash beore (both self hosted open source versions), from my experience I find Metabase a bit easy to work with. Source: about 3 years ago

• Best apps for transitioning from Spreadsheets to SQLite?

  Regarding visualization tools, sqliteviz has proven to be the best I've found so far. Their web app runs locally but has some trackers, so I run it locally via a simple, static HTTP server. Falcon and Redash seem like overkill for my needs. Source: about 3 years ago

• Framework Laptops are now Thunderbolt 4 certified

  In addition to metabase there are redash[0] and apache superset[1]. They are more or less similar to metabase with some different quirks. You can also visualize quite a bit of data in grafana[2] as well. [0] https://redash.io/ [1] https://superset.apache.org/ [2] https://github.com/grafana/grafana. - Source: Hacker News / almost 4 years ago

• How to program an appealing data visualization, that automatically synchronizes itself? (Picture in comments)

  This is typically called a "dashboard" and there is a whole industry of existing commercial products (for example https://redash.io/) that are built around doing data analysis and visualization. Source: almost 4 years ago

GraphQL Cache mentions (4)

• What are the Differences between GQL and REST?

  'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 3 years ago

• GraphQL Is a Trap?

  > Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / over 4 years ago

• GraphQL Is a Trap?

  > Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / over 4 years ago

• Designing a URL-based query syntax for GraphQL

  This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / about 5 years ago