5 ms·

So what did you learn? What were the bugs? GP is referring exactly to your experience - what would this database look like if you kept refining it? I could see

So what did you learn? What were the bugs? GP is referring exactly to your experience - what would this database look like if you kept refining it? I could see this as being very useful for e.g. security system logging, banking and other temporal transactions, even for VCS.

bob1029 3y ago
I learned that single writer principle is maybe the most important thing if you care about performance. If I kept going, we'd have a perfect time traveling database of everything that ever happened in the enterprise. I was even proposing a hashing technique that would provide cryptographic guarantees that our log has not been tampered with, given a pre-shared seed signature. This would be shared with all of our customers and placed in their vaults. At any point, they would be permitted to audit all activity we have logged and recompute our hashes themselves. Really the vision was make B2B consulting with banks and other financial institutions as transparent as possible. Performance was pretty bananas too. Easily outstripped both sql server and SQLite in testing for our hot path by more than 10x. We weren't doing SQL command processing though. Very application-specific access patterns. LMAX Disruptor, or it's equivalent abstraction, will be at the heart of any database I ever attempt to write again.