There's a ton of things I'd be missing to start looking at this.
1. Backend agnostic: let me run on different backends like flink/spark
2. Give me off heap memory please. Let me play dangerous and use pointers directly to optimize interactions with transforms. We wrote our own GC among other things for our tensor lib due to the GC bottlenecks and copying and the like. That's personally what I kind of like about tablesaw.
A library for 1 off adhoc analysis in memory isn't a bad start though, especially since most folks don't actually have that large of problems.
* JavaScript data processing framework for in-browser data processing
* Python framework like pandas
* Big data processing framework like Spark
* Database management system
* Data integration system like typical ETL and BI
* Stream analytics like Kafka Streams
* IoT (light weigh) stream processing engine
* Something else?
I would be very thankful for any suggestion from people who know the market and (acute) needs of the customers. What is the best niche for this kind of technology?
So if I were you, I would do Python DSL, because it addresses my immediate needs of increasing productivity. :)
Maybe you could use calcite[1] as an engine or as a base kind of like arrow.
If you do python, maybe look in pyjnius[2].
There's a lot of things that already have connectors. I would continue along your MVP route allowing folks to do basic things with your framework first then you can improve it as you go. SQL databases aren't a bad initial target. Most folks can do SQL.
[1]: https://calcite.apache.org/ [2]: https://github.com/kivy/pyjnius
There are at least three major questions when we want to introduce a new logical data model:
* How we define columns within one table. Conceptually, it is easy, e.g., SELECT x, y, c = a+b FROM T. Yet, even in this simple case we see a controversy: this statement will create a table but our goal is not to create a table - we want to create a column (function). Bistro uses calc operation for that purpose. But it is of course not new. In pandas, for example, one can use df.apply.
* How to connect several tables. RM, map-reduce and other set-oriented approaches use join which produces a new table. Here we have a similar controversy [1]: I do not want to produce a new table, it is not my goal. My goal is to link these two tables and this means creating a new column. Bistro introduces link operation for such columns.
* How to aggregate data. Here a typical operation is group-by. It is an eclectic operation which combines several other operations and such an approach also has some problems [2]. Bistro changes the way data is aggregated by introducing accumulate functions which get one input (not a subset) and return one output value. An accumulate function is called for each element of the group by updating the current aggregate instead of computing the aggregate by getting the whole group.
So linking and aggregation are what distinguishing Bistro from other approaches and frameworks to data processing including pandas, SQL and map-reduce.
[1] https://www.researchgate.net/publication/301764816_Joins_vs_...
[2] https://www.researchgate.net/publication/316551218_From_Grou...