Googlers share targeted advice for the systems design aspects of Google's interview process for technical and engineering candidates. This video will cover tips for communication, designing to scale, trade-offs and compromises, overall best practices, and more! Skip ahead to: 0:38 - Communication 1:31 - Designing to Scale 2:49 - Concrete and Quantitative Solutions 3:38 - Trade-offs and Compromises 4:18 - Best Practices
Designing to Scale
Questions to keep in mind:
. how can we tell that the system is working
. Is there a bottleneck in the design?
. How do the components work together?
. How do we provide great service to everyone?
System properties:
. Latency
. Throughput
. Storage
Costs of operations:
. Read from disk
. Read from memory
. Local area network (LAN) round-trip
. Cross-continental network
Solution patterns:
. Sharding data
. Replication types
. Write-ahead logging
. Separating data and metadata storage
. Load distribution
Best practice
Explain
Clarify
Improve
Practice
Create for every one, design for every one
Actionable items
Follow up on Oct. 5, 2020
Plan to work on solution patterns. Start from sharding data, replication types, write-ahead logging, separating data and metadata storage, and load distribution.
No comments:
Post a Comment