The Geek Narrator

The Geek Narrator

The GeekNarrator is here to make you curious, excited and inspired about Technology and Software Engineering. You will see in depth technical discussions with actionable insights from the industry experts. These insights will help you get better at Software Engineering, as it comes from the real world engineering experience.

Пікірлер

  • @deepthich2543
    @deepthich25433 күн бұрын

    I saw a small video of tiered storage in StarTree channel but this video is something that is much needed for in-depth understanding of what’s going on. Kudos to Neha for explaining it so clearly.

  • @notrab
    @notrab10 күн бұрын

    Great interview!

  • @VipulVaibhaw
    @VipulVaibhaw10 күн бұрын

    the initial story about how turso was started was awesome!

  • @andreagiammarchi6110
    @andreagiammarchi611010 күн бұрын

    why couldn't LiteFS just observe writes to .wal and propagate only those like you are doing at Turso? Also ... if I understood correctly the primary is location based so you'll have fast primary in Europe, as example, but writings from US will inevitably need to end up there first, right? I think this is also common for other DBs, but I just would like to be confirmed reads are always fast (once in each replica) but writes are also "primary location latency" based. Is this correct? Last, but not least, please don't talk trash on JS, it's pretty awesome after all :P

  • @NaveenSiddareddy
    @NaveenSiddareddy13 күн бұрын

    this is great product .. i will give it a try.. also get quine folks @TheGeekNarrator . think of graph with triggers

  • @padmaraniachanta6885
    @padmaraniachanta688515 күн бұрын

    Iam all persons only onb work love forever ❤️

  • @padmaraniachanta6885
    @padmaraniachanta688515 күн бұрын

    Don't discourage me

  • @padmaraniachanta6885
    @padmaraniachanta688515 күн бұрын

    Where to when i decide and start my life

  • @invgreat5608
    @invgreat560816 күн бұрын

    Great video, Thank you!

  • @AngelMarquez-on8bo
    @AngelMarquez-on8bo16 күн бұрын

    ❤❤❤❤ great talk!

  • @ronyarmon210
    @ronyarmon210Ай бұрын

    Great episode, highly informative regarding search, RDBMs, abd everything in between

  • @nosh3019
    @nosh3019Ай бұрын

    Great episode, I’m a fan of arrow and datafusion

  • @TheGeekNarrator
    @TheGeekNarratorАй бұрын

    Thank you 🙏🏻😀

  • @LeoLeo-nx5gi
    @LeoLeo-nx5giАй бұрын

    This was completely amazing!! Thanks a ton

  • @TheGeekNarrator
    @TheGeekNarratorАй бұрын

    Thanks 🙏🏻

  • @mst2421
    @mst2421Ай бұрын

    What is the name of the app you using for drawings?

  • @TheGeekNarrator
    @TheGeekNarratorАй бұрын

    Goodnotes

  • @VipulVaibhaw
    @VipulVaibhawАй бұрын

    Super cool

  • @padmaraniachanta6885
    @padmaraniachanta688515 күн бұрын

    Dropped all the things no marriage no function only work

  • @patrykkrzyzanski2159
    @patrykkrzyzanski2159Ай бұрын

    Everything wonderful especial the quest. But please do not include this annoying subtitles. When I will then I enable the once from KZread. You're can I not disable. And when I am trying to concentrate on the story, they really annoing

  • @TheGeekNarrator
    @TheGeekNarratorАй бұрын

    Thanks for watching and your feedback. This has been a feedback by many folks so I have removed the captions from the latest episodes. I hope this won’t be a problem going forward.

  • @yosiyosiro3866
    @yosiyosiro3866Ай бұрын

    ​@@TheGeekNarratori disagree to him, the subtitle helps a lot for non-english speaker in understanding the podcast. If you will, at least, please insert it in the caption feature (not the auto-translate one), so we can still activate or deactivate the subtitle

  • @thecloudbaba8668
    @thecloudbaba8668Ай бұрын

    Absolute fruitful discussion, Loved it. looking forward for master Template of Envelope of Estimation :)

  • @AtharvaRao0104
    @AtharvaRao01042 ай бұрын

    What a Masterclass with the Master! Its a great summary of cassandra documentation and parts of it are covered in DDIA. Also, observe how the master crafts concise and clear explanations to the questions. great questions too Kaivalya - Loved it

  • @sampleshawn5380
    @sampleshawn53802 ай бұрын

    thanks a lot for this one, keep going, you are doing really well

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    Thanks a lot 🙏🏻😀

  • @VolodymyrPavlyshyn
    @VolodymyrPavlyshyn2 ай бұрын

    cozodb is also interesting

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    Thanks - I didn’t know about it.

  • @AminSoftwareEngineer
    @AminSoftwareEngineer2 ай бұрын

    Thank you, looking forward for more videos about Cassandra under layers

  • @user-yv9fc4nb8s
    @user-yv9fc4nb8s2 ай бұрын

    Very good introduction. I definitely want to try your product!!!

  • @claytonstangeland
    @claytonstangeland2 ай бұрын

    Excellent in-depth information.

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    Thank you 🙏🏻

  • @jiekun-dev
    @jiekun-dev2 ай бұрын

    Hi Can I re-upload this video to Bilibili with unmodified description and credits?

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    Hi, Sure. Could you please send me an email at [email protected] with more details?

  • @AryanSharma-ys7gr
    @AryanSharma-ys7gr2 ай бұрын

    Awesome Content! Subscribed in a heartbeat, pun intended.

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    Thank you 🙏🏻😀

  • @ksramchandani
    @ksramchandani2 ай бұрын

    What is the corresponding in-memory update for the log that is written? Log is also written to disk or is it in memory and then flushed to disk? What happens when log flushing to disk fails?

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    A Log is flushed to disk, yes. Databases like Postgres also support fsync mode which waits for the log be flushed to the disk, which adds a little performance impact (but nothing comparable to updating data pages and indexes directly). Not using fsync mode OR in simple terms, not waiting for the OS to flush the log to the disk may result in lost committed transactions. Typically a database dealing with concurrent transactions can write log entries to disk with a single fsync which is very efficient. So choose your tradeoff, but the thumb rule I use is, enable fsync by default to ensure maximum reliability and tweak if performance ever become a problem. Does that answer your question?

  • @ksramchandani
    @ksramchandani2 ай бұрын

    @@TheGeekNarrator Yes. Thank you! Wasn't aware of the DB option to wait for log flushing to succeed.

  • @hamzaouni3009
    @hamzaouni30092 ай бұрын

    This was a great video, thanks a lot

  • @apyorbitz
    @apyorbitz2 ай бұрын

    This guest has no idea what they are talking about

  • @bkvinayakkumar9660
    @bkvinayakkumar96603 ай бұрын

    First time ever enjoyed listening to tech like a story felt living in that time... Fabulous! both of you.. The silly mistakes you covered were really spot on with that idea of taking baby steps I could feel the importance of it more now.. this is my take away

  • @TheGeekNarrator
    @TheGeekNarrator3 ай бұрын

    Thank you 🙏🏻

  • @sbera87
    @sbera873 ай бұрын

    Where is the commit log stored? I assume disk. If so, whats the cost of flushing data to disk vs appending to log on disk?

  • @TheGeekNarrator
    @TheGeekNarrator3 ай бұрын

    Yes its on the disk. Appending to log is cheaper because it is sequential and hence no random access. Flushing actual data to disk requires random access which is slower and requires tons of IO depending on what you are inserting/updating/deleting.

  • @akashgoyal2567
    @akashgoyal25672 ай бұрын

    But log is then also prone to getting lost in case of server crashing since they are stored in in-memory before being flushed to disk . What’s the advantage of creating log then structure then ?

  • @TheGeekNarrator
    @TheGeekNarrator2 ай бұрын

    @akashgoyal2567 Typically if durability is important, you would fsync the log (Databases have config for that) which means the log is persisted to the disk. Since it is a sequential write it is way faster and more importantly when DBs have high concurrency one fsync call can be used to write 100s if not 1000s of transaction log to disk. That’s when it becomes really light weight as compared to updating data pages. In short log isn’t lost if you use the right configuration.

  • @NaveenSiddareddy
    @NaveenSiddareddy3 ай бұрын

    I think we are talking about radio technology here philosophically. i listen to radio and think world is in order or not

  • @vignaanjunior382
    @vignaanjunior3823 ай бұрын

    is pub/sub and Kafka does the same ?

  • @TheGeekNarrator
    @TheGeekNarrator3 ай бұрын

    Yes Kafka extends the Pub-Sub model of messaging.

  • @vignaanjunior382
    @vignaanjunior3823 ай бұрын

    ok, thanks for the reply and I did subscribe to your channel. Thanks for your content@@TheGeekNarrator

  • @koteshwarraomaripudi1080
    @koteshwarraomaripudi10803 ай бұрын

    Loved the podcast. Questions and answers were spot on. 👌

  • @KhaPiano
    @KhaPiano3 ай бұрын

    Great introduction - thanks!

  • @bhaskarchiru
    @bhaskarchiru3 ай бұрын

    Very informative video. Wish we have few minutes explaining on-disk layout of data

  • @aus10d
    @aus10d3 ай бұрын

    This was a really fantastic conversation. It was so interesting to hear so many of the details behind tiger beetle. And Joran is a very very good storyteller and the way he explained everything. Just made it a pleasure to listen to. This project is really exciting. Can't wait to see where and how it gets deployed across the world!

  • @TymurYarosh
    @TymurYarosh3 ай бұрын

    Very insightful! For me, the main selling point of Restate is durable execution. However, how Stephan and team hide complexity of execution, communication and persistence into a single platform is a very promising approach to building distributed systems of the new era.

  • @riteshsingh112
    @riteshsingh1123 ай бұрын

    Nice talk and Great initiative. Question about the write path where Broker writes on the page cache. So that means that if leader node fails, data in OS cache will be lost. Does that means that storage devices being used should have the power supplies that can at least let kernel flush all it relevant caches to devices.

  • @jbeasley1880
    @jbeasley18803 ай бұрын

    'Promo sm' 😚

  • @tedspens
    @tedspens3 ай бұрын

    Dude, he's drunk 🍾🍷😅

  • @oussamaabdoune4170
    @oussamaabdoune41703 ай бұрын

    love how he is so energetic and humble thanks for sharing this information

  • @emmanuelbyiringiro7207
    @emmanuelbyiringiro72073 ай бұрын

    I like how is so energetic at his age. You can hate his clean code opinions not his personality

  • @swanv951
    @swanv9513 ай бұрын

    Did support for these transactions make it to Cassandra 5.0? I couldn't find it in the list of new features.

  • @mohamedoueslati462
    @mohamedoueslati4623 ай бұрын

    Thank you for this introduction :)

  • @AAZinvicto
    @AAZinvicto3 ай бұрын

    How do you have so few subscribers, man? your channel is a goldmine

  • @TheGeekNarrator
    @TheGeekNarrator3 ай бұрын

    Thanks a lot 🙏🏻😀

  • @tomaseguchi5793
    @tomaseguchi57934 ай бұрын

    this man is the man, since I met him my life changed, love him!

  • @onkelTom101
    @onkelTom1014 ай бұрын

    Great stuff

  • @onkelTom101
    @onkelTom1014 ай бұрын

    This talk was really awesome esp the explanations he gave were very good. The acid transactions remind me a little bit of conditional writes from Dynamo DB but those here are much better because multi table! Great questions too. The diagrams also help

  • @TheGeekNarrator
    @TheGeekNarrator4 ай бұрын

    Thanks 🙏🏻

  • @timibolu
    @timibolu4 ай бұрын

    Amazing WoooooaaaaHHH 👍👍👍

  • @TheGeekNarrator
    @TheGeekNarrator4 ай бұрын

    Thanks a lot 🙏🏻😀

  • @VipulVaibhaw
    @VipulVaibhaw4 ай бұрын

    kudos kaivalya!!

  • @TheGeekNarrator
    @TheGeekNarrator4 ай бұрын

    Thanks a lot Vipul 🙏🏻😀