quix VS Redash

Aerospike Data Browser is basically a stack that consists of Quix, Presto, and the Aerospike Connector for Presto, and is dockerized. Figure 1 depicts an under the hood view. The Quix UI provides a DB Explorer and a SQL editor, in addition to a notebook manager for managing your notebooks. Presto exposes a JDBC interface to Quix and uses the Aerospike Connector to translate SQL queries into API calls to the DB. Building a stack with the aforementioned components for a desktop installation is not trivial by any means. Presto can scale to 100’s of nodes for a large scale deployment, but we wanted to limit the data browser to a single Presto instance that would run both the coordinator and worker in the developer's desktop environment. Our initial size of the Presto docker image was over 2GB, which was not acceptable. Hence, we stripped out all but the Aerospike connector from the plugin directory. Similarly, we had to downsize the Quix connector. Finally, we got the compressed docker image size under 1GB. We also made a design decision to default to schema inference so that a user that does not know the schema apriori is not left out.

It seems like there may be an issue with Watchdog on Apple Silicon.

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 processes, but of course authentication would be required.

Yeah, a lot of the time I'd agree with you.

This container came about for the Redash project (https://github.com/getredash/redash), which has been stuck on PostgreSQL 9.5 (!) for years.

Moving to a new PostgreSQL container version is easy enough for new installations, but rolling that kind of change out to an existing userbase isn't so pretty.

For people familiar with the command line, PostgreSQL, and Docker then no worries.

But a large number of Redash deployments seem to have been done by people not skilled in those things. "We deployed it from the Digital Ocean droplet / AWS image / etc!"

For those situations, something that takes care of the database upgrade process automatically is the better approach. :)

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

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.

Redash seems to be dead or at least in hibernation. There hasn't been a release in over a year.

https://github.com/getredash/redash/issues/5891

redash