Computing in the Cloud
Venue : AC04 - 007
Time : 3:10 pm - 4:40 pm
Instructor : Manu Awasthi (firstname.lastname@example.org)
Office Hours : After lectures, or by appointment
Contacting Course staff
The recommended method for contacting course staff is through the email alias email@example.com. We will be filtering emails regarding the course based on this email alias. Individual emails to course staff will not be answered.
Suggested Books and Readings
Designing Data-Intensive Applications by Martin Kleppmann
Software Engineering at Google: Lessons Learned from Programming Over Time by Titus Winters, Tom Manshreck & Hyrum Wright
The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines (Second Edition) by Luiz André Barroso, Jimmy Clidaras and Urs Hölzle
The Cloud Computing Book : The Future of Computing Explained by Douglas Comer
Understanding Distributed Systems: What Every Developer Should Know About Large Distributed Applications by Roberto Vitillo
Online Learning Management System
We will be using Google Classroom as the Learning Management System (LMS) for this course. You will automatically be added to the Google Classroom for this course via Ashoka AMS. All the course material will be made available through the either Google Classroom, or as links on this webpage.
We will be accepting student submissions only through Google Classroom. No email submissions will be considered.
The following is a tentative guideline for the grading policy and may undergo a change.
Assignments and Projects - 70%
The bulk of the assessment for the course will be done through a group project which will require student groups (2 or 3 students per group) to implement an end to end SaaS application. To earn credit, major and minor milestones for the project will be need to be met by project groups. These milestones will be made available at the start of the course
Project Presentation + Report: 20%
Class participation : 10%
Project Deadlines (Tentative)
15/09/2022 (End of class): Group formation. Groups size of 2 is preferred, 3 will be acceptable. Send your group to the teaching staff.
29/09/2022: Project proposal due. Please discuss with the instructor before deciding on the projects.
11/10/2022: First checkpoint report due.
01/11/2022: Second checkpoint report and demo due.
08/12/2022: Final everything due. This includes report , code, analysis.
Reading Week: Final presentation and demos.
Cheating and Plagiarism
CS2465 has a zero tolerance for cheating, even for assignments.
NOTE: Any evidence of academic integrity violation / plagiarism will result in an F grade for the entire course, no exceptions. In addition, you will be reported to the OAA for academic integrity violation.
There is no mandatory attendance, but there is a class participation component to your eventual grade. However, you are expected to attend all the lectures. There will be material covered in class that is not present in textbooks. In addition, some portion of the lectures will be used for discussions. It is in your best interests to attend the lectures as they happen, and get your questions answered during the discussions, rather than waiting till the end of the semester.
The instructor reserves the right to cold call on any student who is attending the class to elicit student participation. You don't necessarily need to provide a correct answer to the question being posed, but it will be expected that everyone at least attempt to provide an answer.
The instructor gratefully acknowledges instruction material (slides, figures, animations etc.) that have been created by a number of instructors for similar courses around the world.