NANODEGREE PROGR AM SYLL ABUS

Cloud Native
Application
Architecture
Overview
In this program, students will learn to run and manage scalable applications in a cloud native environment,
using open source tools and projects like ArgoCD, gRPC and Grafana. Students will learn to identify the
best application architecture solutions for an organization’s needs, design a microservice architecture
by leveraging cloud native tools and patterns, implement best practices in Kubernetes security, and use
dashboards to diagnose, troubleshoot and improve site reliability.

IN CO L L A B O R AT I O N W I T H

Prerequisites:
• Understand the
Estimated Time:
basics of http
4 Months at
• Basic Python
10hrs/week
• Ability to use Git,
Linux machines
and Linux
Command Line
• Familiar with
web application
development in
any language

Technical Mentor
Flexible Learning:
Support:
Self-paced, so
Our knowledgeable
you can learn on
mentors guide your
the schedule that
learning and are
works best for you.
focused on answering
your questions,
motivating you and
keeping you on track

Cloud Native Application Architecture | 2

Course 1: Cloud Native Fundamentals
Throughout this course, students will learn how to structure, package and release an application to
a Kubernetes cluster, while using an automated CI/CD pipeline. Students will start by applying a suite
of good development practices within an application, package it with Docker and distribute it through
DockerHub. This will transition to the exploration of Kubernetes resources and how these can be used to
deploy an application. At this stage, students will be comfortable using k3s to bootstrap a lightweight and
functional Kubernetes cluster. Next, students will examine template configuration managers, such as Helm,
to implement the parameterization of Kubernetes declarative manifests. Towards the end of the course,
students will learn the fundamentals of Continuous Integration and Continuous Delivery (CI/CD) with GitHub
Actions and ArgoCD and completely automate the release process for an application.

TechTrends is an online website used as a news sharing platform

that enables users to access the latest news within the cloud-native
ecosystem. Students will need to extend the project to export and
visualize the logs, metrics and status of the application. They will
Course Project 1: apply their acquired knowledge to package, store and distribute the
TechTrends code as a Docker image. In its turn, the artifact (or Docker image)
will be deployed to a cluster using Kubernetes resources, such as
deployments and services. By the end of the project, students will
use Helm to template the Kubernetes manifests and automate the
TechTrends project release using GitHub Actions and ArgoCD.

LEARNING OUTCOMES

Welcome to • Evaluate the cloud native ecosystem

LESSON ONE Cloud Native • Explore CNCF (Cloud Native Computing Foundation) and
Fundamentals cloud native tooling

• Choose monolith or microservice based-architecture for an

Architecture application
Consideration
LESSON TWO • Consider and evaluate the involved trade-offs for monoliths
for Cloud Native
and microservices
Applications
• Apply good development practices to an application

• Use Docker to package an application and distribute it via

DockerHub
Container • Bootstrap a Kubernetes cluster using k3s
LESSON THREE Orchestration
with Kubernetes • Explore Kubernetes resources for an application deployment
• Differentiate between declarative and imperative
Kubernetes management techniques

Cloud Native Application Architecture | 3

 LEARNING OUTCOMES

• Understand the usage and abstracted components while

LESSON FOUR Open Source PaaS using a Platform as a Service (PaaS) solution
• Explore application deployment with Cloud Foundry

• Explain CI/CD and its benefits

• Apply Continuous Integration fundamentals using GitHub
Actions
CI/CD with Cloud
LESSON FIVE • Apply Continuous Delivery fundamentals using ArgoCD
Native Tooling
• Use Helm, as a configuration template manager, to
parametrize declarative Kubernetes manifests
• Deploy an application using ArgoCD and a Helm chart

Cloud Native Application Architecture | 4

Course 2: Message Passing
In this course, students will learn how to refactor microservice capabilities from a monolithic architecture
and employ different forms of message passing in microservices. To begin, students will create a migration
strategy to refactor a service from a monolith to its own microservice and implement the migration. Next,
students will be introduced to industry standard best practices for message passing in a service architecture.
Finally, students will focus on design decisions and the implementations of different forms of message passing
in development and production systems.

In this project, students will refactor UdaConnect, an existing

application that facilitates professional networking at conference
and trade shows. UdaConnect ingests and uses location data to
Course Project 2: find connections between individuals who have been near one
another at an event. The current version of the application is built
Refactor UdaConnect as a proof-of-concept with a monolith architecture. Your task is to
apply strategies that you have learned in the course to refactor
this application into a microservice architecture and implement
message passing strategies to improve its design.

LEARNING OUTCOMES

• Define message passing

Introduction to
LESSON ONE • Understand historical context of how and why message
Message Passing
passing is used

• Analyze and identify the first service or capability to

decompose a monolith
• Create a dependency map in order to prioritize how to
Refactoring From refactor a service (based on business logic)
LESSON TWO
a Monolith • Determine the appropriate migration strategy
• Migrate a service from a monolith into its own microservice
• Apply the strangler pattern for migrating a monolith
architecture

Cloud Native Application Architecture | 5

 LEARNING OUTCOMES

• Identify use cases & implement best practices of REST

Types of Message • Identify use cases of gRPC
LESSON THREE
Passing • Identify use cases & implement best practices of message
queues

• Use and apply REST

Implementing
LESSON FOUR • Use and apply gRPC
Message Passing
• Use and apply Kafka

• Identify use cases of communication protocol in conjunction

Message Passing with one another
LESSON FIVE
in Production • Use OpenAPI
• Manage the life cycle of communication protocol

Cloud Native Application Architecture | 6

Course 3: Observability
This course covers the fundamentals of observability in distributed systems. Today, Kubernetes has become
the de facto standard for cloud native applications and is widely used for distributed systems. To be
effective as an observability expert, it is critical to understand how to monitor and respond to the health and
performance of both your Kubernetes clusters and the applications hosted on them. This course will teach
students how to collect system performance data using Prometheus, how to collect application tracing data
using Jaeger and how to visualize the results in a dashboard using Grafana.

In this project, you will install and use the basic tools required
to perform application tracing and performance monitoring,
including Jaeger and Prometheus. You will then learn how to
Course Project 3: deploy and use Grafana to create dashboards and graphs
to visualize performance and trace data collected in the
Building a Metrics Kubernetes cluster. Finally, you will practice the day-to-day
Dashboard operations of a reliability engineer, such as planning SLIs and
filing tickets.

LEARNING OUTCOMES

Introduction • Distinguish between black box and white box monitoring

LESSON ONE to Cloud • Identify the stakeholders involved in observability
Observability • Identify the key tools needed to run a kubernetes cluster

• Recognize the distinct roles that Prometheus, Grafana and

Observability Jaeger play in observability
LESSON TWO
Tools • Successfully install Prometheus, Grafana and Jaeger on a
Kubernetes cluster

Cloud Native Application Architecture | 7

 LEARNING OUTCOMES

• Identify the role observability plays in modern applications

SLOs, SLIs and
LESSON THREE • Recognize why we use SLOs and SLIs as metrics
Error Budgets
• Use error budgets to make observability decisions

• Distinguish tracing from logging and identify the benefits

tracing provides beyond standard logging
LESSON FOUR Tracing • Identify the basics of how a span is used when tracing
applications
• Identify the basics of how Jaeger helps manage a trace

Building • Navigate Grafana and set up data sources

LESSON FIVE
Dashboards • Create dashboards and panels with various metrics

Cloud Native Application Architecture | 8

COURSE 4: Microservices Security
In this course, students will learn how to harden a Docker and Kubernetes microservices architecture. To
begin, students will learn STRIDE to threat model and reason about microservice security. Next, students will
dig deep to explore the Docker and Kubernetes attack surface and be introduced to industry open-source
tools such as Docker-bench and Kube-bench to evaluate and harden Docker and Kubernetes weaknesses.
Students will then learn about software composition analysis with Trivy and Grype to evaluate image layers
and common application security vulnerabilities and provide remediation. Finally, students will deploy
runtime security monitoring to introspect running microservices for security signals and learn how to respond
to a security incident.

In this project, students will be presented with a real-life

scenario to threat-model and harden a Kubernetes environment
in response to security concerns brought to them by their
company’s CTO. Students will use an openSUSE base image
Course Project 4: to create a hardened Docker container and deploy it to a
Hardened Microservices Docker Hub image registry. Students will then use it to deploy
a Kubernetes cluster with a pre-configured Falco DaemonSet
Environment and harden the cluster using what we learned from the course.
Students will introduce a security incident intentionally, then work
on identifying the payload, remediating it and conducting a post-
mortem. Students will create alerting for this payload, review
lessons learned and write an incident response report.

LEARNING OUTCOMES

Introduction to • Define microservices security

LESSON ONE Microservices • Understand the difference between microservices security
Security and traditional infrastructure security

• Examine the STRIDE methodology for threat modeling as

part of the Software Development Lifecycle (SDLC)
Threat Modeling • Apply the STRIDE methodology to the primary Docker
LESSON TWO
with STRIDE components
• Apply the STRIDE methodology to the primary Kubernetes
components

Cloud Native Application Architecture | 9

 LEARNING OUTCOMES

• Apply Docker security properties in-depth, including client,

host and registry, evaluating threat models
Docker Attack
• Implement CIS benchmarks to harden docker images via
LESSON THREE Surface Analysis
docker-bench
and Hardening
• Implement image signing using Docker content trust to
verify the integrity of the image

• Examine Kubernetes security properties in-depth, including

Kubernetes Attack cloud-controller-manager, etcd, kube-apiserver, kube-
LESSON FOUR Surface Analysis controller-manager, kube-proxy and kube-scheduler
and Hardening • Evaluate findings against CIS benchmarks and apply a
methodology for hardening and testing changes

• Examine examples of supply chain tampering with recent

Solarwinds incidents and why software analysis composition
Software is vital to security
LESSON FIVE Composition • Examine common application security vulnerabilities and
Analysis provide remediation
• Examine and remediate common vulnerable libraries and
application security vulnerabilities in a Flask application

• Examine security considerations for dangerous commands

and ongoing runtime security
Runtime • Implement Sysdig Falco as a DaemonSet with a basic rule
LESSON SIX Monitoring and set to monitor node processes and send to Grafana for
Incident Response visualization and alerting
• Define a security response playbook to triage and respond
to alerts

Cloud Native Application Architecture | 10

Our Classroom Experience
REAL-WORLD PROJECTS
Build your skills through industry-relevant projects. Get
personalized feedback from our network of 900+ project
reviewers. Our simple interface makes it easy to submit
your projects as often as you need and receive unlimited
feedback on your work.

KNOWLEDGE
Find answers to your questions with Knowledge, our
proprietary wiki. Search questions asked by other students,
connect with technical mentors, and discover in real-time
how to solve the challenges that you encounter.

WORKSPACES
See your code in action. Check the output and quality of
your code by running them on workspaces that are a part
of our classroom.

QUIZZES
Check your understanding of concepts learned in the
program by answering simple and auto-graded quizzes.
Easily go back to the lessons to brush up on concepts
anytime you get an answer wrong.

CUSTOM STUDY PLANS

Create a custom study plan to suit your personal needs
and use this plan to keep track of your progress toward
your goal.

PROGRESS TRACKER
Stay on track to complete your Nanodegree program with
useful milestone reminders.

Cloud Native Application Architecture | 11

 Learn with the Best

Katie Gamanji Justin Lee

DATA P L AT F O R M E N G I N E E R AT
E CO S Y S T E M A D V O C AT E F O R C N C F
S T I TC H F I X
(C L O U D N AT I V E CO M P U T I N G F O U N D AT I O N )

Katie is the Ecosystem Advocate for CNCF Justin is an engineer specializing in

(Cloud Native Computing Foundation), designing modern data platforms
steering the End User Community. Katie’s and scalable systems. He has been a
focus is to foster the growth and visibility consultant for Fortune 500 companies
of the End User Community while bridging and has traveled the world to work with
the gap with other ecosystem units, such his clients. He provides mentorship
as project maintainers, TOCs and SIGs. and interviews developers through
In the past roles, Katie contributed to Codementor and has a BS in Computer
the build-out of platforms that gravitate Science from UCLA.
towards cloud-native principles and open-
source tooling, with Kubernetes as the
focal point. These projects started with
the automation of application delivery
on OpenStack-based infrastructure,
which transitioned into the creation of a
centralized, globally distributed platform
at Condé Nast.

Cloud Native Application Architecture | 12

 Learn with the Best

Nick Reva Jason “Jay” Smith

T E C H N I C A L M A N AG E R , E N G I N E E R I N G A P P M O D E R N I Z AT I O N S P E C I A L I S T AT
S E C U R I T Y, S N A P C H AT G O O G L E C LO U D
Nick has been working in Security Jason “Jay” Smith is an App Modernization
Engineering his entire career, for over 14 Specialist at Google Cloud. Jay has over
years now. Over the last five years, he’s 15 years experience in technology and
been a Technical Manager leading teams open source solutions. Currently Jay helps
to build highly scalable security services Google Cloud customers modernize their
at tech companies, including SpaceX and application platforms using best practices
Snapchat. In his current role at Snapchat, in cloud native technologies. Prior to
he lead security engineering teams to joining Google, Jay had worked for other
build and maintain security services organizations while also leading his own.
across our cloud native environment.
Snapchat are big fans of open source and
CNCF projects like Envoy.

Cloud Native Application Architecture | 13

All Our Nanodegree Programs Include:

EXPERIENCED PROJECT REVIEWERS

REVIEWER SERVICES

• Personalized feedback & line by line code reviews

• 1600+ Reviewers with a 4.85/5 average rating
• 3 hour average project review turnaround time
• Unlimited submissions and feedback loops
• Practical tips and industry best practices
• Additional suggested resources to improve

TECHNICAL MENTOR SUPPORT

MENTORSHIP SERVICES

• Questions answered quickly by our team of

technical mentors
• 1000+ Mentors with a 4.7/5 average rating
• Support for all your technical questions

PERSONAL CAREER SERVICES

C AREER SUPPORT

• Github portfolio review

• LinkedIn profile optimization

Cloud Native Application Architecture | 14

Frequently Asked Questions
PROGR AM OVERVIE W

WHY SHOULD I ENROLL?

Cloud native architecture has been described as the future of application
development. This program was designed to help you take advantage of the
growing need for skilled cloud native architects.

WHAT JOBS WILL THIS PROGRAM PREPARE ME FOR?

The need for a strong cloud native culture in an enterprise organization is
greater than ever. The skills you will gain from this Nanodegree program will
qualify you for jobs in several industries as countless companies are trying to
keep up with digital transformation.

HOW DO I KNOW IF THIS PROGRAM IS RIGHT FOR ME?

The course is for individuals who are looking to advance their careers as cloud
native architects. This is an intermediate course that requires fluency in basic
python programming as well as a basic understanding of http, the command
line and developing web applications.

ENROLLMENT AND ADMISSION

DO I NEED TO APPLY? WHAT ARE THE ADMISSION CRITERIA?

No. This Nanodegree program accepts all applicants regardless of experience
and specific background.

WHAT ARE THE PREREQUISITES FOR ENROLLMENT?

A well-prepared learner will meet the following prerequisites:
• Understand the basics of http (like client, server and internet request)
• Basic Python (data types, Functions, REST requests, web development)
• Ability to use Git, Linux machines and Linux Command Line
• Familiar with web application development in any language
• Familiarity with Docker, exposure to a CI/CD pipeline is not required for
success in this program but is a helpful prerequisite skill to have.

IF I DO NOT MEET THE REQUIREMENTS TO ENROLL, WHAT SHOULD I DO?

If you believe you need more preparation, here are some additional Udacity
programs that can get you up to speed: Intro to Computer Science, Linux
Command Line Basics, Intro to Programming and Front End Web Developer.

Cloud Native Application Architecture | 15

FAQs Continued
TUITION AND TERM OF PROGR AM

HOW IS THIS NANODEGREE PROGRAM STRUCTURED?

The Cloud Native Application Architecture Nanodegree program is comprised
of content and curriculum to support 5 projects. We estimate that students can
complete the program in 4 months working 10 hours per week.
Each project will be reviewed by the Udacity reviewer network. Feedback will be
provided and if you do not pass the project, you will be asked to resubmit the
project until it passes.

HOW LONG IS THIS NANODEGREE PROGRAM?

Access to this Nanodegree program runs for the length of time specified above.
If you do not graduate within that time period, you will continue learning with
month to month payments. See the Terms of Use and FAQs for other policies
regarding the terms of access to our Nanodegree programs.

CAN I SWITCH MY START DATE? CAN I GET A REFUND?

Please see the Udacity Nanodegree program FAQs for policies on enrollment in
our programs.

SOF T WARE AND HARDWARE

WHAT SOFTWARE AND VERSIONS WILL I NEED IN THIS PROGRAM?

There are no software and version requirements to complete this Nanodegree
program. All coursework and projects can be completed via Student Workspaces
in the Udacity online classroom.

Cloud Native Application Architecture | 16