diagraphic
It's definitely over-engineered for most use cases. The code base has grown to handle everything from cross-platform file I/O to transaction recovery, with way more documentation than probably necessary.
Not claiming it's production-ready or faster than the battle-tested options out there, but as an experimental solution to concurrency bottlenecks it's rather cool. :)
I'd love to hear your thoughts. Always happy to discuss the design or answer questions.
I've been writing code for 15+ years, this made me laugh my ass off. Comments are great, I don't read comments but I write them for others, especially for open source code. Atoi may be something you and I and a whole bunch of others know but people who don't it's a fine comment. Relax! :)
Cloudflare Outage
I hope you check it out :) happy to answer any questions!
WildcatDB
Show HN: This database never puts you on hold
https://github.com/wildcatdb/wildcat
Hey everyone! I hope you’re all having a great day. Today I’m sharing an experimental open-source project I’ve been working on for the past few months called Wildcat. Wildcat is an embedded persistent storage engine implementing an lsm tree similar to RocksDB and or LevelDB. The motivation for this system was to try to solve the multi-writer bottlenecks that most embedded systems incur. ...