Clojurians Log v2

@alekcz360 There is no minimum speed requirement, but it would be nice for users to know some performance metrics of course. Something we should provide in konserve itself including plotting.

The versioning is to be able to do online migration, i.e. when you decide to change the storage format you can detect that before you read an old value and trigger a migration. This is an internal design decision, but it has proven necessary, since otherwise you need to manually detect the version which might require more IO. If you prefer to do offline migration, e.g. to not violate SLAs on key access, you can just read all keys.

For the file store we currently encode the version in the first byte.

I'm thinking something needs to be in the test suite so that if someone refactors something they aren't going to impact application performance downstream or in datahike itself

I can't seem to find it in the filestore.clj. What line does it happen on?

I think it is not pushed yet. Ferdi is working on it again on Friday, hopefully we can get it pushed until next week, we will see.

Konserve can be used without Datahike in different scenarios, some stores, such as S3, might be slow by their very nature, yet still valuable.

Cool cool. Thanks.