Terrific video with great, simple explanations. The whole time I was hoping for a few more recipes that I think are frequent use cases. Is it possible to cover them as well? My suggestions: 1. Leader election 2. Partition assignment in consistent hashing 3. Id assignment in Snowflake ID generation (I recognize that 2 & 3 are similar but it may be instructive to show why). I also think you make a great point about linearizable writes vs strong consistency. But I am unsure about the implications of the choices that ZK makes. I would love if you would double click on that. What exactly are we losing? Why is what we have enough?
1) have an ephemeral node called leader, only one person can have it at a time haha, conditionally write to it if it doesn't exist 2) covered in the Kafka video, each partition is a node and you can claim them from machines 3) I have to look into what a snowflake ID is but assuming it's monotonically increasing probably something like a sequential node, or have an ID assigning node claim a lock in ZK to have the right to assign IDs. For your last question, it really depends on what you're trying to do. Can your application tolerate a machine briefly having stale config? What are the implications?
Random but I wonder what you’ve been up to career wise after leaving google? I can’t imagine that just making these vids maintains your finances. Plus with all this system design knowledge, did it lead to an easy L4/L5 offer elsewhere despite leaving Google as L3? Or does it just not matter in this market.
I work in high frequency trading at the moment, where we don't have levels, so I'm unfortunately not able to answer that question. I know I'm capable of passing systems design interviews, but another component of whether a company wants to extend me an offer as a senior engineer comes down to whether I have "senior engineer experience".
I’m all seriousness, I like this format. Describing the paper then some applications help put things into perspective
Terrific video with great, simple explanations. The whole time I was hoping for a few more recipes that I think are frequent use cases. Is it possible to cover them as well? My suggestions:
1. Leader election
2. Partition assignment in consistent hashing
3. Id assignment in Snowflake ID generation (I recognize that 2 & 3 are similar but it may be instructive to show why).
I also think you make a great point about linearizable writes vs strong consistency. But I am unsure about the implications of the choices that ZK makes. I would love if you would double click on that. What exactly are we losing? Why is what we have enough?
1) have an ephemeral node called leader, only one person can have it at a time haha, conditionally write to it if it doesn't exist
2) covered in the Kafka video, each partition is a node and you can claim them from machines
3) I have to look into what a snowflake ID is but assuming it's monotonically increasing probably something like a sequential node, or have an ID assigning node claim a lock in ZK to have the right to assign IDs.
For your last question, it really depends on what you're trying to do. Can your application tolerate a machine briefly having stale config? What are the implications?
I feel that after watching this channel for year or even less I will be definitely promoted from senior to staff swe 😅
Thank you ! . I'm learning a lot because of you.
Hey, absolutely love ur videos, i was wondering if you could make a video on elasticache?
Perhaps in the future if it's got an interesting paper!
Original paper is from 2010 according to google citation. But i also found an apache doco with a ©️ 2008
yo jordan, if you write a book, i'll buy it
You ever seen the kama sutra? I wrote that
@@jordanhasnolife5163lmao
I love this furry channel
another great video by the legend
Zookeeper not being strongly consistent feels like a knife to the back. I like the Onesie - I was a shark for Halloween.
Call him a shark cause he eats like that
Love your content
What a cute hoodie!
you should do a system design breakdown on Nvidia Geforce now!!!
Is that not just recording on your computer lol
@@jordanhasnolife5163 no lol the cloud computing engine lol
@@jordanhasnolife5163 *cloud computing gaming engine
I was wearing it at first as well didn’t know it was Halloween tho
Lol
Dancing bear? Great content!
Random but I wonder what you’ve been up to career wise after leaving google? I can’t imagine that just making these vids maintains your finances. Plus with all this system design knowledge, did it lead to an easy L4/L5 offer elsewhere despite leaving Google as L3? Or does it just not matter in this market.
I work in high frequency trading at the moment, where we don't have levels, so I'm unfortunately not able to answer that question. I know I'm capable of passing systems design interviews, but another component of whether a company wants to extend me an offer as a senior engineer comes down to whether I have "senior engineer experience".