This was always the plan, and if you look closer at VSR and the state machine interface you’ll see it’s already pluggable. We just haven’t packaged it. (We’re dogfooding our first few internal “CustomBeetles” before we package and document.)
replyIn about 5 years time the trend will be "Just use Beetles" for everything :P
replySeriously Can't wait to see this.
Congrats on launching [1] Tigerbeetle Cloud. Should have submitted that as well but I thought this was more interesting. May be another time.
Ah thank you! (and for posting!)
replyThat’s the dream. To serve the world’s transactions and data (with a whole lotta beetles!). We’re working to make it reality.
Appreciate the congrats! You make today a double whammy! :P
That's cool! I will be then probably taking a closer look!
replyThanks! Watch IronBeetle too on Twitch if you’d like to go really deep.
replyEmphasis on: opinionated custom databases. One database might be SQL-based for periodic report generation. Another database might be a noSQL key-val store designed to effortless grow with the number of end-users. General-purpose programming languages already cater to the 'own business logic' part - it's their whole job. What's left? System architecture, networking features, consensus. That's Kafka.
replyllvm for databases?
replyIsn’t that literally what Turso said they wanted to be?
replyI'm pretty sure they manage to get that level of performance and reliability, since they have a very limited schema.
replyI'm pretty sure you can't just do a precise 128 byte align, if one of the element is an image blob or varchar(1000).
No, the LSM in TB is generalizable at comptime to any combination of power of two sized key/value tuples.
reply