|
![]() |
![]() |
![]() |
![]() |
|
![]() |
The following is a list of topics covered in this course, and their approximate order. Readings are expected to be completed before lecture of that day. Wed, Jan 3We will explore the underlying concepts behind the MapReduce system:
Project: Mon, Jan 8In day 2, we will introduce parallel systems. In particular, we will discuss design considerations for creating a parallelized architecture. Project: Wed, Jan 10Together with our understanding of Project: Project 1 released;
begin thinking about project 2
Tue, Jan 16Alden's lab hours cancelled Wed, Jan 17Albert and Hannah will have make-up office hours from 2:30-3:30 in the lab and will be available for scoping project 2 proposals. In class, we will discuss MapReduce paper in groups, focusing on its design assumptions and tradeoffs. Project: Project 1 continues;
continue thinking about project 2
Thu, Jan 18Project: Project 1 due at 6 PM Fri, Jan 19Project: Project 2 initial proposals due (via email) Mon, Jan 22We will do an in-depth study of Sawzall, Google's logging infrastructure built on MapReduce. Project: Incorporate project 2 feedback
Wed, Jan 24Tech talks from Googlers Project: All project 2 feedback
returned; begin project work in earnest
Fri, Jan 26Project: Final project 2 proposals due Mon, Jan 29More tech talks from GooglersProject: Continue working on project 2
Wed, Jan 31We will give a high-level overview of the GFS architecture and introduce principles of distributed system design.Project: Continue working on project 2
Mon, Feb 12Presentation day will occur several weeks after lectures have completed. Students will have a chance to present their completed project 2 to Google engineers as well as other students. Project: Project 2 completed
|