Is this project abandoned? about pumpkindb HOT 3 OPEN

I'm also circling back to this project.

I could invest some time in it as availability allows, but before that I'd need more documentation to learn how it can be used in an ES scenario. Even if there are problems, incomplete features, etc - I should be able to understand the problems as an user before attempting to fix them.

Please, more docs, especially for programmers who don't know MUMPS or forth.

from pumpkindb.

I guess my answer is the obvious one. We're building a product in which the timeline of user events is to be queried very frequently and cannot be an expensive operation. Both in a per user and across all users or a set of them. Traditional relational databases are sub optimal in the sense that they don't provide a cheap way to iterate over the top elements of an ordered set of elements. We have a couple of tables which already show signs of being a bottleneck and they are not even that large.

Traildb appears to be on to something, but it rejects the need to easily append data as a design choice. This is almost an immediate deal breaker for us.

The concept you link looks like materialization of the typical use case. Personally I think that pumpkindb api is a bit too low level for most end users. I, for one, would need at least more documentation to use it. Viewdb is perhaps the materialization of a very specific use case. Traildb has, in my opinion, the right level of abstraction, but this is also a matter of personal preference.

from pumpkindb.

The project is on hiatus right now. It was a little bit more of a rabbit hole that I anticipated and some original design decisions were less that optimal.

That said, I am very interested in building a platform for the ideas behind this concept, but not sure what form exactly will they take. PumpkinDB was originally created for the purpose of powering a database like this.

Where would usefulness of this software come from for you, if you don't mind me asking?

from pumpkindb.