It's not clear if this will actually hit your use case or not.
Specifically, low overhead means different things to different people.
Also, my suggestion is not a database -- it is an analytics engine. The
persistence part of the problem is off the table at this time, too. I
wanted to mention it up
Hi,
I'm trying to build something like an embedded data base system around
arrow with some properties which I will list below.
The question is if someone can point me to existing solutions (or attempts)
for such kind of problem.
I'm trying to develop a data layout such that
* typically reading is
