A few years ago I was lucky enough to lead a small team that got to develop a large new distributed system. The project was/is quite successful, quickly replacing the previous, scaling up well, and being stable. During early code reviews I often had a couple of pieces of feedback:
- Never hold a mutex while doing anything that may block.
- Don't set deadlines on RPCs.
These were informed by working on and debugging previous systems like
Bigtable and other complex distributed systems. I repeated them so much, that eventually they were transcribed as Maloney's Laws. Over the next few years probably 30+ engineers contributed to the project, many went on to new projects and some even began to cite these laws to other engineering teams.
Now I know that these laws as stated here may be overly-simplistic. But given the way Google builds systems internally, they are good rules of thumb. Of course like all rules, there are exceptions.
I will explore the logic behind these two rules in follow up posts.
Coding is tough. At least for me, it is. I never understand it – that’s why I chose to take up writing as a profession. I am happy providing Blog Content Service and getting paid for it. But I have to say you are good at explaining things. I will follow your future posts to see if I can learn a thing or two about coding by reading your content.
ReplyDeletecasino, poker room, blackjack, bingo
ReplyDeletecasino, goyangfc poker room, blackjack, bingo room, blackjack, bingo room, poker https://vannienailor4166blog.blogspot.com/ room, poker room, poker room, https://deccasino.com/review/merit-casino/ poker room, wooricasinos.info poker room, poker worrione.com room,
There are even times when Ifeel so down but I will feel better right after checking your blogs. You have made me feel so good about myself all the time and please know that I do appreciate everything that you have.well. Keep writing such amazing sweatshirts for women stuff alwaysI will always let you and your words women handbags
ReplyDelete