dupver VS qrono

I work with a lot of uncompressed structured binary files so I finally broke down and wrote my own system based on the Restic chunker: https://github.com/akbarnes/dupver

I wound up writing dupver https://github.com/akbarnes/dupver after getting frustrated with the lack of versioning tools for binary files. One neat thing about .docx files and their ilk is that they are "just" zip files so it isn't hard to add special handling to pull out their contents and run deduplication over that.

DupVer https://github.com/akbarnes/dupver is a deduplicating version control system for large binary files. It's designed to keep state in a repository on the local machine separate from the working directory so it plays nice with cloud synchronization software.

I started it after constant headaches involving Git LFS and the corporate proxy. It's based around the Restic chunker library, with inspiration from both the Duplicacy backup software and Boar, another binary version control system for large binary files.

https://github.com/akbarnes/dupver

https://qrono.net, https://github.com/c2nes/qrono

A work in progress, Qrono is a persistent, time-ordered queue server providing at-least-once delivery. The time-ordering can be used to schedule values to be delivered in the future, implement exponential backoff within a consumer, etc.

In addition to HTTP and gRPC interfaces, Qrono supports a RESP (https://redis.io/topics/protocol) interface allowing Redis tools (e.g. redis-cli) and clients to be used.