Skip to content

Commit bd8eaa7

Browse files
committedMar 5, 2025·
update
1 parent aea0a5d commit bd8eaa7

File tree

3 files changed

+4
-6
lines changed

3 files changed

+4
-6
lines changed
 

‎public/deployment-info.txt

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Timestamp: 2025-03-05T13:33:32Z
1+
Timestamp: 2025-03-05T13:37:08Z
22
Repository: https://github.com/acailic/awesome-scalability-talks
33
DeployedAt: https://acailic.github.io/awesome-scalability-talks
4-
Version: 34818f4
4+
Version: aea0a5d

‎src/stores/tabStore.ts

+2-2
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ interface TabState {
77
initializationTab: () => void;
88
setActiveTab: (tab: String) => void;
99
}
10-
const DEFAULT_TAB = TAB.ARTICLES;
10+
const DEFAULT_TAB = TAB.TALKS;
1111

1212
export const useTabStore = create<TabState>((set, get) => ({
13-
activeTab: "talks",
13+
activeTab: DEFAULT_TAB,
1414
isInitialized: false,
1515
setActiveTab: (tab) => set({ activeTab: tab }),
1616
initializationTab: () => {

‎src/talks/04-building-a-distributed-build-system-at-google-scale-sum.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# Building a Distributed Build System at Google Scale
2-
31
In her insightful talk, Aysylu Greenberg takes us on a journey through Google's evolution of build systems at massive scale. She walks through the fascinating challenges of supporting 30,000 engineers across 40 offices who collectively make 45,000 commits per day to a two-billion-line codebase. The story unfolds with the transition from a simple push-based architecture to a more resilient pull-based system called "Build Service" that gracefully handles the immense scale of Google's monolithic repository.
42

53
Greenberg illustrates how Google's distributed build system, "Build Rabbit," sits at the heart of their developer infrastructure, orchestrating five million daily builds that generate petabytes of build artifacts. She shares the careful migration strategy that allowed the team to transition between architectures with zero downtime - an impressive feat given the system's critical position in Google's development workflow. The tale is not just about technical architecture but about thoughtful system design that balances centralized versus distributed control planes, making it possible to evolve complex systems while continuously serving users.

0 commit comments

Comments
 (0)
Please sign in to comment.