TigerBeetle: A Trillion Transactions [video]
youtube.com
TigerBeetle: A Trillion Transactions [video]
1–10 of 37 posts
Re: TigerBeetle: A Trillion Transactions [video]
#2TigerBeetle's Joran Greef is a teacher / explainer par excellence.
Re: TigerBeetle: A Trillion Transactions [video]
#3TigerBeetle's Joran Greef is a teacher / explainer par excellence.
Ah I appreciate your kind words, Aditya!
This was a team effort: the object storage connector, the scale test, the visualization, the slides, even provisioning the hardware had its challenges!
Re: TigerBeetle: A Trillion Transactions [video]
#4TigerBeetle's Joran Greef is a teacher / explainer par excellence.
Ah I appreciate your kind words, Aditya! This was a team effort: the object storage connector, the scale test, the visualization, the slides, even provisioning the hardware had its challenges!
Oh most certainly; I am remiss to have not included the group effort in my comment, particularly as a person surrounded by theatre and film making friends.
Still, for the same reason, I have some idea of why their productions turn out well (or not). Where "well" is "a story well told", not "successful" as in "did well at the box office". The why is usually one person who keeps asking the questions and making the decisions that take the story from imagination to imagination via screen or floor.
Something tells me your doubtlessly excellent "production team" (in film terms) will agree with my original comment :)
Re: TigerBeetle: A Trillion Transactions [video]
#5The takeaway is that you can just buy a single beefy server instead of using kubernetes or whatever.
Re: TigerBeetle: A Trillion Transactions [video]
#6The takeaway is that you can just buy a single beefy server instead of using kubernetes or whatever.
To a first approximation, yes. But, why? And for up to how many hundred terabytes of data can you get away with the single beefy server? Provided you make what design choices?
Which leads to the real takeaway which is "Tiger Style": https://tigerstyle.dev/ which I am partial to, along with Rich Hickey's "Hammock Driven Development" https://www.youtube.com/watch?v=f84n5oFoZBc
"Tiger on Hammock" will absolutely smoke the competition.
(edit: add links)
Re: TigerBeetle: A Trillion Transactions [video]
#7The takeaway is that you can just buy a single beefy server instead of using kubernetes or whatever.
"Always has been"
Re: TigerBeetle: A Trillion Transactions [video]
#8I think I need a deeper-dive into the "diagonal scaling" presented. From my understanding, this is actually no different from "industry decoupling" he disparages earlier in the presentation. There are even off-the-shelf libraries for LSMs backed by object storage like SlateDB.
Re: TigerBeetle: A Trillion Transactions [video]
#9I think I need a deeper-dive into the "diagonal scaling" presented. From my understanding, this is actually no different from "industry decoupling" he disparages earlier in the presentation. There are even off-the-shelf libraries for LSMs backed by object storage like SlateDB.
I feel the Expression Problem neatly frames the "diagonal scaling" proposition; what system design choices will allow the architecture to scale vertically in what fashion, while also being able to scale what horizontally, without losing strict serialisability.
If we add a "vertical" capability, it cannot be at the cost of any existing "horizontal" capability, nor should doing so forfend any future "horizontal" capability. And vice-versa (adding horizontal capability should not mess with vertical ones). The point at which one will break the other is the theoretical design limit of the system.
Re: TigerBeetle: A Trillion Transactions [video]
#10The takeaway is that you can just buy a single beefy server instead of using kubernetes or whatever.
And your beefy server goes down what do you do? Where do you think those object storage live exactly?
Kubernetes is not just for scaling, it's a way to standardize all ops.