Skip to content
0:00 / 0:00

#jeffdean#google#latency

Building Software Systems At Google and Lessons Learned

Stanford

2.2M subscribers • 18 videos on Hallway

YouTube
  • Recommended by 5 people: 4 on Hacker News and 1 curated list.
  • A classic. People kept recommending it from 2012 to 2022.
  • Presented by Jeff Dean, Google Senior Fellow

Intermediate. Assumes working knowledge.

256K views15 years ago5 recommendations

Distributed systemsSystems programmingScaling and large-scale architectureSoftware architecture

Jeff Dean shares lessons on designing and scaling Google's software infrastructure, emphasizing latency numbers and system evolution.

(November 10, 2010) Speaker Jeffrey Dean describes some of his experiences at Google and the types of technology being used today. He talks about how their technology has evolved over time and how their technological infrastructure has allowed them to be so successful. Stanford University: stanford.edu/ School of Engineering: soe.stanford.edu/ Stanford Center for Professional Development: scpd.stanford.edu/ Stanford University Channel on YouTube: youtube.com/stanford

Why it's here

5 people recommend this

What people say. Widely recommended as a classic talk on system design, scaling, and understanding latency numbers.

bouloson Hacker News • Recommends

On “Ask HN: What's your favorite tech talk?”

In addition to Linus's git talk, I really enjoyed Jeff Dean's EE380 retrospective on Building Systems at Google ( link to this video ). Many people have mentioned Jeff's basic premise elsewhere ("Design a system for 10x your current need, but not 100x, rewrite it before then") but this talk gave several useful examples where tipping points occurred (at least with Search).

Coding Interview Universitycurated list on GitHubRecommends

Under “System Design, Scalability, Data Handling”

Jeff Dean - Building Software Systems At Google and Lessons Learned (video)

kqr2on Hacker News • Recommends

On “Latency Numbers Every Programmer Should Know”

Also recommend Jeff Dean's tech talk Building Software Systems At Google and Lessons Learned which references those latency numbers. Slides: link Video: link to this video Also, a previous thread on latency numbers: link

ma2rtenon Hacker News • Recommends

On “Web Performance Profiling: Google.com”

There is a lecture from Jeff Dean about it: link to this video It's from 2010, but the fundamentals probably haven't changed.

mrazomoron Hacker News • Recommends

On “We're improving search results when you use quotes”

Probably this one: link Or this one: link to this video (terrible audio) Both are very old, but extremely well aged. IMO, the secret behind Google Search is not the smartness of the algorithms, but how much of it is baked in those O(100ms) which takes Google machines to answer your query. That's why the links above are the true reason Google Search performs well. Natural Language Processing and Information Retrieval state of the art is far beyond what Google/Bing/Yahoo/Yandex/Baidu employ. But, it's far too expensive to serve it at QPS & latency required for decent UX.

ignoramouson Hacker News • Mentions

On “AWS Nitro System”

Google is famous for publishing a lot of material every year. A couple of related publications you might be interested in: 1. The Datacenter as a computer: link 2. The SRE book: link A couple of dated presentations: 1. Jeff Dean on building software systems at Google (2010) at Stanford: link to this video 2. Notes by James Hamilton on a talk by Jeff Dean on Google Datacenters in 2008: link -- Microsoft Research pretty much work on bleeding edge tech, as well and publish about some of their research pretty regularly. Here's a staring point to help anyone interested find relevant publications: link