605.702.8VL - Cloud-native Architecture and Microservices

Expanded Course Description

Programing experience is required.
Prior cloud experience is required.

This course will teach students how to design, develop, deploy, and maintain cloud-native applications using various tools and frameworks. Students will learn the principles and practices of cloud computing, such as scalability, elasticity, resilience, and automation. Students will also gain hands-on experience with popular cloud platforms and services, such as AWS, Azure, Google Cloud, Kubernetes, Docker, and Serverless. Students will be able to apply their knowledge and skills to real-world scenarios and challenges in the cloud-native domain.

Course Structure

The course materials are divided into modules which can be accessed by clicking Modules on the course menu. A module will have several sections including the overview, content, readings, discussions, and assignments. You are encouraged to preview all sections of the module before starting. Most modules run for a period of seven (7) days, exceptions are noted in the Course Outline. You should regularly check the Calendar and Announcements for assignment due dates.

Course Topics

Part I: Cloud-native computing
Part I: Event Driven architecture
Part I: Kafka, messaging
Part II: Containers
Part II: Kubernetes
Part II: Kubernetes in cloud
Part II: Service Mesh
Part III: Serverless Computing
Part III: Cloud-native security
Part III: Cloud Security

Course Goals

By the end of the course, you will be able to:

• Understand the concepts, principles, and practices of cloud-native architecture, microservices, and serverless computing.
• Learn how to design, develop, test, and deploy cloud-native applications using various tools and frameworks.
• Gain hands-on experience with microservices, Kubernetes through exercises and projects.
• Explore the advanced topics in cloud-native architecture such as observability, security, resilience, scalability, and DevOps.

Textbooks

Required

• Raj, P., Vanga, S., & Chaudhary, A. (2022). Cloud-Native Computing: How to Design, Develop, and Secure Microservices and Event-Driven Applications. John Wiley & Sons.

ISBN: 978-1119814764

• Emison, J. (2023). Serverless as a Game Changer: How to Get the Most Out of the Cloud. Addison-Wesley Signature Series

ISBN: 978-0137392629

Optional

• FreeWheel Biz-UI Team (2023). Cloud-Native Application Architecture: Microservice Development Best Practice, Springer

 ISBN: 978-9811997815

Other Materials & Online Resources

Must have an account with one cloud provider: AWS, Azure

Required Software

You need access to at least one cloud service: AWS, Azure or GCP

Student Coursework Requirements

Preparation and Participation (10% of Final Grade Calculation)

You are responsible for carefully reading all assigned material and being prepared for discussion. The majority of readings are from the course text. Additional reading may be assigned to supplement text readings.

Post your initial response to the discussion questions by the evening of day 3 for that module week. Posting a response to the discussion question is part one of your grade for module discussions (i.e., Timeliness).

Part two of your grade for module discussion is your interaction (i.e., responding to classmate postings with thoughtful responses) with at least two classmates (i.e., Critical Thinking). Just posting your response to a discussion question is not sufficient; we want you to interact with your classmates. Be detailed in your postings and in your responses to your classmates' postings. Feel free to agree or disagree with your classmates. Please ensure that your postings are civil and constructive.

I will monitor module discussions and will respond to some of the discussions as discussions are posted. In some instances, I will summarize the overall discussions and post the summary for the module.

Evaluation of preparation and participation is based on contribution to discussions.

Preparation and participation is evaluated by the following grading elements:

Timeliness (50%)

Critical Thinking (50%)

Preparation and participation is graded as follows:

• 100–90 = A—Timeliness [regularly participates; all required postings; early in discussion; throughout the discussion]; Critical Thinking [rich in content; full of thoughts, insight, and analysis].
• 89–80 = B—Timeliness [frequently participates; all required postings; some not in time for others to read and respond]; Critical Thinking [substantial information; thought, insight, and analysis has taken place].
• 79–70 = C—Timeliness [infrequently participates; all required postings; most at the last minute without allowing for response time]; Critical Thinking [generally competent; information is thin and commonplace].
• <70 = F—Timeliness [rarely participates; some, or all required postings missing]; Critical Thinking [rudimentary and superficial; no analysis or insight is displayed].

Assignments (50% of Final Grade Calculation)

The class is separated into three parts, and each part will have its own assignment totaling 50% of the final grade. 

Each assignment requires the student to build/develop a system using one of the three cloud providers (AWS, Azure, GCP).  The system is built based on the current technology stack being discussed in the class: messaging, queuing, containers, kubernetes, or serverless. 

Each assignment also requires a written portion that explains in detail the system being built and the features/capabilities of the system. 

All assignments are due according to the dates in the Calendar.

Late submissions will be reduced by one letter grade for each week late (no exceptions without prior coordination with the instructors).

If, after submitting a written assignment you are not satisfied with the grade received, you are encouraged to redo the assignment and resubmit it. If the resubmission results in a better grade, that grade will be substituted for the previous grade.

Qualitative assignments are evaluated by the following grading elements:

1. Working end-to-end solution (40%)
2. Requirements of the assignment met with regards to the components to use (40%)
3. Assignment write-up is of high quality and technical accuracy (20%) (Writing is expected to meet or exceed accepted graduate-level English and scholarship standards. That is, all assignments will be graded on grammar and style as well as content. APA standards related to proper referencing is required)

Quantitative assignments are graded as follows:

• 100–90 = A—All parts of question are addressed; All assumptions are clearly stated; All intermediate derivations and calculations are provided; Answer is technically correct and is clearly indicated; Answer precision and units are appropriate.
• 89–80 = B—All parts of question are addressed; All assumptions are clearly stated; Some intermediate derivations and calculations are provided; Answer is technically correct and is indicated; Answer precision and units are appropriate.
• 79–70=C—Most parts of question are addressed; Assumptions are partially stated; Few intermediate derivations and calculations are provided; Answer is not technically correct but is indicated; Answer precision and units are indicated but inappropriate.
• <70=F—Some parts of the question are addressed; Assumptions are not stated; Intermediate derivations and calculations are not provided; The answer is incorrect or missing; The answer precision and units are inappropriate or missing.

Course Group Project (40% of Final Grade Calculation)

A course project will be assigned several weeks into the course. The next-to-the-last week will be devoted to the course project.  Proposal for the team project is due during part II of the term (date to be announced).  Your teams must be at least 3 people.   The proposal and eventually the completed project *must* meet a set of requirements that are given in the project scope.  The group project will have specific non-functional requirements that must be met in addition to the functional requirements. 

The course project is evaluated by the following grading elements:

1. Acceptable proposal that will demonstrate key topics of the term (10%)
2. Completed end-to-end working solution (50%)
3. Completeness of the report and detailed architectural and cost analysis (20%)
4. Non-functional requirement 1 – TBD (10%)
5. Non-functional requirement 2 – TBD (10%)

Course Project is graded as follows:

• 100–90 = A—Student Preparation and Participation/ Team Preparation and Participation [individual/ team roles and responsibilities well defined and understood; individual/ team well versed in use of Adobe Connect; individual/ team work product(s) agreed to, well prepared and available to all team members/ instructors]; Student Understanding/ Team Understanding [rich in content; full of thought, insight, and analysis].
• 89–80 = B—Student Preparation and Participation/ Team Preparation and Participation [individual/ team roles and responsibilities well defined and understood; individual/ team well versed in use of Adobe Connect; individual/ team work product(s) agreed to and prepared]; Student Understanding/ Team Understanding [substantial information; thought, insight, and analysis has taken place].
• 79–70 = C—Student Preparation and Participation/ Team Preparation and Participation [individual/ team roles and responsibilities agreed to; individual/ team well versed in use of Adobe Connect; individual/ team work product(s) prepared]; Student Understanding/ Team Understanding [generally competent; information is thin and commonplace].
• <70 = F—Student Preparation and Participation/ Team Preparation and Participation [individual/ team roles and responsibilities not well understood; individual/ team has difficult with use of Adobe Connect; individual/ team work product(s) partially prepared]; Student Understanding/ Team Understanding [rudimentary and superficial; no analysis or insight displayed].

Grading Policy

Course Policies

No late assignments will be accepted.   

Academic Policies

Deadlines for Adding, Dropping and Withdrawing from Courses

Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.

Academic Misconduct Policy

All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.

This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.

Students with Disabilities - Accommodations and Accessibility

Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.

For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.

Student Conduct Code

The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically. 

For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/

Classroom Climate

JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity. 
 
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).

Course Auditing

When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.