Octosql-plugin-random_data Alternatives

Similar projects and alternatives to octosql-plugin-random_data

steampipe

146 6,391 9.7 Go octosql-plugin-random_data VS steampipe

Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
materialize

117 5,580 10.0 Rust octosql-plugin-random_data VS materialize

The data warehouse for operational workloads. (by MaterializeInc)
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
octosql

34 4,699 1.2 Go octosql-plugin-random_data VS octosql

OctoSQL is a query tool that allows you to join, analyse and transform data from multiple databases and file formats using SQL.
noria

26 4,925 0.0 Rust octosql-plugin-random_data VS noria

Fast web applications through dynamic, partially-stateful dataflow
cargo-semver-checks

18 921 9.4 Rust octosql-plugin-random_data VS cargo-semver-checks

Scan your Rust crate for semver violations.
dsq

20 3,634 4.3 Go octosql-plugin-random_data VS dsq

Commandline tool for running SQL queries against JSON, CSV, Excel, Parquet, and more.
go-sqlite3-stdlib

6 123 0.0 Go octosql-plugin-random_data VS go-sqlite3-stdlib

A standard library for mattn/go-sqlite3 including best-effort date parsing, url parsing, math/string functions, and stats aggregation functions
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
octosql-plugin-postgres

1 2 0.0 Go octosql-plugin-random_data VS octosql-plugin-postgres

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better octosql-plugin-random_data alternative or higher similarity.

Suggest an alternative to octosql-plugin-random_data

octosql-plugin-random_data reviews and mentions

Posts with mentions or reviews of octosql-plugin-random_data. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-14.

OctoSQL allows you to join data from different sources using SQL
13 projects | news.ycombinator.com | 14 Jul 2022

Hey!
> I think the main fundamental difference is that this wants all of the data upfront in a data file.
Absolutely not! Moreover, OctoSQL can push down predicates to databases so that it only has to download a small subset of the table, if the datasource and query allow it.
> Very easy to model HTTP APIs as a table.
"Very easy" is relative, but you can take a look at the random_data[0] datasource which is exactly this. I'm also planning to add a GitHub datasource fairly soon. That said, there is Steampipe[1] for which this is the main use case afaik (hitting API's and exposing them as tables through Postgres FWD's written in Go), so it might be a smoother and more polished experience. There's also tons of plugins already available for it.
> Easy to model basically anything as a table for example files on my filesystem.
Yep, definitely. That's the idea behind OctoSQL. Strive to create a tool for easily exposing anything through SQL (like your machine's processes list, an API, and join that with a file, or database). There's still lot's of documentation work left to do though, in order to make the plugin authoring experience easier.
> A decent query planner so that I can avoid expensive things (like API calls) if I can determine if I need the object based on something cheaper (like a local disk access).
Probably depends on the use-case, and it sometimes needs you to be fairly explicit, but OctoSQL does in fact do that. It will push down predicates to underlying databases, which means joining something small with something very big (while only taking very small amounts of the latter) can be very fast with LOOKUP JOIN's.
> I want something that is easy to extend to sources that are possibly non-listable or at the very least I don't want to have all of the data available.
Doable. An example of this is the `plugins.available_versions` table[2]. It requires you to provide the plugin name as a predicate, as the versions need to be downloaded from the plugin's own repository (and listing all plugin repositories on each query isn't really what you want to be doing). You can also LOOKUP JOIN with the `plugins.available_plugins` table if that is indeed what you want.
[0]: https://github.com/cube2222/octosql-plugin-random_data
[1]: https://steampipe.io
[2]: https://github.com/cube2222/octosql/blob/main/datasources/pl...