Dissecting GitHub Outage: Downtime due to an Edge Case

[@manish-mk]

Wow.. you're uploading so much content nowadays. And all of these are worth watching. Keep Going !

[@AsliEngineering]

I love sharing what I know 😀

[@AdityaRaval7017]

Thanks Arpit for these detailed explanation, your videos are very informative and I learn something new everytime I watch them.

[@dhruvilshah9098]

Thank you so much Learned a lot from this video, do make more video's like this, Thankss!!!

[@AsliEngineering]

Thanks. There are so many videos like this already on the channel. Have a playlist called Outage Dissection. Check that out of you haven't already.

[@dhruvilshah9098]

@@AsliEngineering Yeah Sure Thankss

[@typicalindiancoderwhowatch8458]

Well this was some out of the box topic with good content 👌👌

[@Bluesky-rn1mc]

Thanks Arpit, really informative content

[@AsliEngineering]

Thanks a ton 🤘

[@d4devotion]

you just gave me a hint, where I need to change my application guard rate where we are taking 10000 as limit by default if no limit is provided from front-end. I am going to change to somewhat 10 or 100.

[@AsliEngineering]

Whoaaa. So happy it was helpful. These small make the difference. Just one correction: it is guard rail and not guard rate. My bad I should have pronounced it better.

[@anirbanb1908]

I know this is hypothetical but don't you think if there is a composite index authorId_1_createdAt_-1, it should still work fine?

[@rahulbera454]

Happened with me too, we missed an edge case in code ( SQL query ) that was retrieving our entire user table having millions of rows 🫡