Lately we started using release "names" alphabetically to understand what is deployed where, cause as I told, we have bunch of clouds, and full release cycle is usually 1 month, so during this period we might have 2-3 different versions deployed at the same time.

I decided to bring a bit of Lineage Lore to the releases. Do you remember this IMBA game in 2007?

If anybody asks me, where I want to return and never leave that place - it will be Dion town + music ambience:
https://www.youtube.com/watch?v=pdEoZ7RdrMI&ab_channel=GatsuLT

Tomorrow 2025-03-09 is stream at 19:00 UTC.
If you have any questions / ideas/ suggestions for the stream - leave them here.

For now the agenda:
- couple of Leetcode questions
- implementing and load testing our rate limiter system design solution (adding Redis)
- questions from the videos and shorts.
- talk about oncall

Started:
https://www.twitch.tv/andreyka26_
https://www.youtube.com/watch?v=ysVLvtmCepI&ab_channel=andreyka26_se

Here we go) first incident. To my luck - false positive, no impact, and most probably misconfigured monitor, on another team’s side

Meanwhile, let's solve classic:
https://leetcode.com/problems/implement-trie-prefix-tree/?envType=study-plan-v2&envId=leetcode-75

Lets goooo. Same shit for different region. Pretty tandom, all false positive, all coming not from our monitoring. Dont know how to disable, and want to sleep

This Shit cannot even wait for me to get to the office

It is still raining, later I will share the story with you. But in general, when it is raining like that, you cannot just go for a lunch or something without laptop. So yeah, oncall started well 😁

RAINIIIIING

Probably the worst oncall day ever

Half of them are sev2 which we downgraded to sev3.

For reference, sev2 incident makes the tool to ring your phone.

https://leetcode.com/problems/non-overlapping-intervals/description/?envType=study-plan-v2&envId=leetcode-75

Problem for the evening)

Solution should be n log n