OctoSQL VS ReactiveX

OctoSQL[0] or DuckDB[1] will most likely be much simpler, while going through 10 GB of JSON in a couple seconds at most. Disclaimer: author of OctoSQL [0]: https://github.com/cube2222/octosql. - Source: Hacker News / about 1 year ago

This is really cool! With their Postgres scanner[0] you can now easily query multiple datasources using SQL and join between them (i.e. Postgres table with JSON file). Something I strived to build with OctoSQL[1] before. It's amazing to see how quickly DuckDB is adding new features. Not a huge fan of C++, which is right now used for authoring extensions, it'd be really cool if somebody implemented a Rust extension... - Source: Hacker News / about 1 year ago

Congrats on the Show HN! It's great to see more tools in this area (querying data from various sources in-place) and the Lambda use case is a really cool idea! I've recently done a bunch of benchmarking, including ClickHouse Local and the usage was straightforward, with everything working as it's supposed to. Just to comment on the performance area though, one area I think ClickHouse could still possibly improve... - Source: Hacker News / over 1 year ago

SPyQL is really cool and its design is very smart, with it being able to leverage normal Python functions! As far as similar tools go, I recommend taking a look at DataFusion[0], dsq[1], and OctoSQL[2]. DataFusion is a very (very very) fast command-line SQL engine but with limited support for data formats. Dsq is based on SQLite which means it has to load data into SQLite first, but then gives you the whole breath... - Source: Hacker News / over 1 year ago

To add somewhat of a counterpoint to the other response, I've tried the Steampipe CSV plugin and got 50x slower performance vs OctoSQL[0], which is itself 5x slower than something like DataFusion[1]. The CSV plugin doesn't contact any external API's so it should be a good benchmark of the plugin architecture, though it might just not be optimized yet. That said, I don't imagine this ever being a bottleneck for the... - Source: Hacker News / over 1 year ago

DynamicData is a .NET library that brings the power of reactive programming to collections. It is built upon the principles of Reactive Extensions (Rx), extending these concepts to handle collections like lists and observables more efficiently and flexibly. DynamicData provides a set of tools and extensions that enable developers to manage collections reactively, meaning any changes in the data are automatically... - Source: dev.to / 13 days ago

Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read. Source: about 1 year ago

The thing that really irks me is that the generator pattern doesn't have to be an OO-first feature. Observable streams[1] work with the same basic foundation and those are awesome for FP. [1]: https://reactivex.io/. - Source: Hacker News / about 1 year ago

> I’m not sure what you mean by "Rx" in this context. From “reactive extensions”, a proper name for a family of libraries[1] (RxJava, Rx.NET, RxJS), AFAICT one of the first attempted implementations of mature FRP ideas in the imperative world and one messy enough that it took React for anything similar to reënter the mainstream. Compare the enthusiastic HN reception of “Deprecating the observer pattern” in... - Source: Hacker News / about 1 year ago

Here’s what you can do with the observer pattern — https://reactivex.io/. Source: over 1 year ago