From 01fc16750a583cff2535d8ee52305bdb2911670d Mon Sep 17 00:00:00 2001 From: Vidhi Ruparel Date: Fri, 5 Jun 2026 16:10:59 +0530 Subject: [PATCH] feat: add Cloud Computing chapter content with all units --- app/components/subjects.tsx | 12 +- app/sem5/Cloud-Computing/[Chapter]/page.tsx | 171 ++++++++++++++++++ .../Cloud-Computing/components/sidebar.tsx | 83 +++++++++ app/sem5/Cloud-Computing/constants.ts | 43 +++++ app/sem5/Cloud-Computing/content/chapter0.tsx | 95 ++++++++++ app/sem5/Cloud-Computing/content/chapter1.tsx | 103 +++++++++++ .../Cloud-Computing/content/chapter10.tsx | 29 +++ .../Cloud-Computing/content/chapter11.tsx | 28 +++ .../Cloud-Computing/content/chapter12.tsx | 27 +++ .../Cloud-Computing/content/chapter13.tsx | 30 +++ .../Cloud-Computing/content/chapter14.tsx | 36 ++++ .../Cloud-Computing/content/chapter15.tsx | 35 ++++ .../Cloud-Computing/content/chapter16.tsx | 45 +++++ .../Cloud-Computing/content/chapter17.tsx | 34 ++++ .../Cloud-Computing/content/chapter18.tsx | 45 +++++ .../Cloud-Computing/content/chapter19.tsx | 35 ++++ app/sem5/Cloud-Computing/content/chapter2.tsx | 38 ++++ .../Cloud-Computing/content/chapter20.tsx | 32 ++++ .../Cloud-Computing/content/chapter21.tsx | 39 ++++ .../Cloud-Computing/content/chapter22.tsx | 34 ++++ .../Cloud-Computing/content/chapter23.tsx | 45 +++++ .../Cloud-Computing/content/chapter24.tsx | 48 +++++ .../Cloud-Computing/content/chapter25.tsx | 38 ++++ .../Cloud-Computing/content/chapter26.tsx | 46 +++++ .../Cloud-Computing/content/chapter27.tsx | 52 ++++++ .../Cloud-Computing/content/chapter28.tsx | 37 ++++ app/sem5/Cloud-Computing/content/chapter3.tsx | 30 +++ app/sem5/Cloud-Computing/content/chapter4.tsx | 55 ++++++ app/sem5/Cloud-Computing/content/chapter5.tsx | 39 ++++ app/sem5/Cloud-Computing/content/chapter6.tsx | 34 ++++ app/sem5/Cloud-Computing/content/chapter7.tsx | 32 ++++ app/sem5/Cloud-Computing/content/chapter8.tsx | 43 +++++ app/sem5/Cloud-Computing/content/chapter9.tsx | 28 +++ app/sem5/Cloud-Computing/layout.tsx | 16 ++ app/sem5/Cloud-Computing/page.jsx | 147 +++++++++++++++ lib/course/CloudComputing.js | 138 ++++++++++++++ 36 files changed, 1819 insertions(+), 3 deletions(-) create mode 100644 app/sem5/Cloud-Computing/[Chapter]/page.tsx create mode 100644 app/sem5/Cloud-Computing/components/sidebar.tsx create mode 100644 app/sem5/Cloud-Computing/constants.ts create mode 100644 app/sem5/Cloud-Computing/content/chapter0.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter1.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter10.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter11.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter12.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter13.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter14.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter15.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter16.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter17.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter18.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter19.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter2.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter20.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter21.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter22.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter23.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter24.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter25.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter26.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter27.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter28.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter3.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter4.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter5.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter6.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter7.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter8.tsx create mode 100644 app/sem5/Cloud-Computing/content/chapter9.tsx create mode 100644 app/sem5/Cloud-Computing/layout.tsx create mode 100644 app/sem5/Cloud-Computing/page.jsx create mode 100644 lib/course/CloudComputing.js diff --git a/app/components/subjects.tsx b/app/components/subjects.tsx index 724b848..8399b31 100644 --- a/app/components/subjects.tsx +++ b/app/components/subjects.tsx @@ -123,9 +123,15 @@ const subjectCodes: Record = { "Decision Sciences": "des", "Software Engineering": "se", }; - +const customHrefs: Record = { + "cc": "/sem5/Cloud-Computing", + "cd": "/sem5/cd", + "cle": "/sem5/cle", +}; // Available subjects -const available = ["ep", "c", "em1", "em2", "oops", "dsc", "coa", "os", "ml", "dops", "cd", "cle","ec"]; +const available = ["ep", "c", "em1", "em2", "oops", "dsc", "coa", "os", "ml", "dops", "cd", "cle","ec","cc"]; + + export default function SubjectsSection() { return ( @@ -154,7 +160,7 @@ export default function SubjectsSection() {
{list.map((subj) => { const code = subjectCodes[subj]; - const href = `/${semCode}/${code}/ch0`; + const href = customHrefs[code] ?? `/${semCode}/${code}/ch0`; const isAvailable = available.includes(code); const baseClass = diff --git a/app/sem5/Cloud-Computing/[Chapter]/page.tsx b/app/sem5/Cloud-Computing/[Chapter]/page.tsx new file mode 100644 index 0000000..7bee0ca --- /dev/null +++ b/app/sem5/Cloud-Computing/[Chapter]/page.tsx @@ -0,0 +1,171 @@ +import Link from "next/link"; +import { Righteous } from "next/font/google"; +import { ArrowBigLeft, ArrowBigRight } from "lucide-react"; +import { chapters } from "../constants"; + +const righteous = Righteous({ + subsets: ["latin"], + weight: "400", + variable: "--font-righteous", +}); + +// Map chapter id to content component +import { Ch0Content } from "../content/chapter0" +import { Ch1Content } from "../content/chapter1"; +import { Ch2Content } from "../content/chapter2"; +import { Ch3Content } from "../content/chapter3"; +import { Ch4Content } from "../content/chapter4"; +import { Ch5Content } from "../content/chapter5"; +import { Ch6Content } from "../content/chapter6"; +import { Ch7Content } from "../content/chapter7"; +import { Ch8Content } from "../content/chapter8"; +import { Ch9Content } from "../content/chapter9"; +import { Ch10Content } from "../content/chapter10"; +import { Ch11Content } from "../content/chapter11"; +import { Ch12Content } from "../content/chapter12"; +import { Ch13Content } from "../content/chapter13"; +import { Ch14Content } from "../content/chapter14"; +import { Ch15Content } from "../content/chapter15"; +import { Ch16Content } from "../content/chapter16"; +import { Ch17Content } from "../content/chapter17"; +import { Ch18Content } from "../content/chapter18"; +import { Ch19Content } from "../content/chapter19"; +import { Ch20Content } from "../content/chapter20"; +import { Ch21Content } from "../content/chapter21"; +import { Ch22Content } from "../content/chapter22"; +import { Ch23Content } from "../content/chapter23"; +import { Ch24Content } from "../content/chapter24"; +import { Ch25Content } from "../content/chapter25"; +import { Ch26Content } from "../content/chapter26"; +import { Ch27Content } from "../content/chapter27"; +import { Ch28Content } from "../content/chapter28"; + +const chapterComponents: Record = { + ch0: Ch0Content, + ch1: Ch1Content, + ch2: Ch2Content, + ch3: Ch3Content, + ch4: Ch4Content, + ch5: Ch5Content, + ch6: Ch6Content, + ch7: Ch7Content, + ch8: Ch8Content, + ch9: Ch9Content, + ch10: Ch10Content, + ch11: Ch11Content, + ch12: Ch12Content, + ch13: Ch13Content, + ch14: Ch14Content, + ch15: Ch15Content, + ch16: Ch16Content, + ch17: Ch17Content, + ch18: Ch18Content, + ch19: Ch19Content, + ch20: Ch20Content, + ch21: Ch21Content, + ch22: Ch22Content, + ch23: Ch23Content, + ch24: Ch24Content, + ch25: Ch25Content, + ch26: Ch26Content, + ch27: Ch27Content, + ch28: Ch28Content, +}; + +type Props = { params: Promise<{ Chapter: string }> }; + +export default async function ChapterPage({ params }: Props) { + const { Chapter: chapterId } = await params; + + const chapterData = chapters.find((c) => c.id === chapterId); + const currentIndex = chapters.findIndex((c) => c.id === chapterId); + const prevChapter = currentIndex > 0 ? chapters[currentIndex - 1] : null; + const nextChapter = currentIndex < chapters.length - 1 ? chapters[currentIndex + 1] : null; + + if (!chapterData) { + return ( +
+

Chapter not found

+ + Return to Chapter 1 + +
+ ); + } + + const ChapterComponent = chapterComponents[chapterId]; + + return ( +
+
+

+ Cloud Computing +

+ +

+ {chapterData.title} +

+ +
+ {prevChapter ? ( + + Previous + + ) :
} + + {nextChapter ? ( + + Next + + ) :
} +
+ +
+ + {ChapterComponent ? ( + + ) : ( +
+

Coming Soon

+

+ This chapter is under development. Check back soon! +

+
+ )} +
+ +
+ {prevChapter ? ( + + {prevChapter.title} + + ) :
} + + {nextChapter ? ( + + {nextChapter.title} + + ) :
} +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/components/sidebar.tsx b/app/sem5/Cloud-Computing/components/sidebar.tsx new file mode 100644 index 0000000..a187d77 --- /dev/null +++ b/app/sem5/Cloud-Computing/components/sidebar.tsx @@ -0,0 +1,83 @@ +"use client"; +import { Righteous } from "next/font/google"; +import Link from "next/link"; +import { usePathname } from "next/navigation"; +import { useState, useEffect } from "react"; +import { chapters } from "../constants"; + +const righteous = Righteous({ + subsets: ["latin"], + weight: "400", + variable: "--font-righteous", +}); + +export default function Sidebar() { + const pathname = usePathname(); + const [open, setOpen] = useState(false); + + useEffect(() => { + if (window.innerWidth >= 768) { + setOpen(true); + } + }, []); + + return ( + <> +
setOpen(false)} + /> + +
+ + + +
+ + ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/constants.ts b/app/sem5/Cloud-Computing/constants.ts new file mode 100644 index 0000000..4b7c4db --- /dev/null +++ b/app/sem5/Cloud-Computing/constants.ts @@ -0,0 +1,43 @@ +export type Chapter = { + id: string; + title: string; + subTopics?: SubTopic[]; +}; + +export type SubTopic = { + id: string; + title: string; + isPage?: true; +}; + +export const chapters: Chapter[] = [ + { id: "ch0", title: "Course Outline" }, + { id: "ch1", title: "What is Cloud Computing" }, + { id: "ch2", title: "Cloud Computing Models" }, + { id: "ch3", title: "Benefits and Challenges" }, + { id: "ch4", title: "Cloud vs On-Premises" }, + { id: "ch5", title: "Infrastructure as a Service (IaaS)" }, + { id: "ch6", title: "Platform as a Service (PaaS)" }, + { id: "ch7", title: "Software as a Service (SaaS)" }, + { id: "ch8", title: "Comparing Service Models" }, + { id: "ch9", title: "Public Cloud" }, + { id: "ch10", title: "Private Cloud" }, + { id: "ch11", title: "Hybrid Cloud" }, + { id: "ch12", title: "Community Cloud" }, + { id: "ch13", title: "Cloud-Native Architecture" }, + { id: "ch14", title: "Microservices Architecture" }, + { id: "ch15", title: "Scalability Patterns" }, + { id: "ch16", title: "High Availability & Disaster Recovery" }, + { id: "ch17", title: "Identity & Access Management" }, + { id: "ch18", title: "Data Protection" }, + { id: "ch19", title: "Network Security" }, + { id: "ch20", title: "Compliance & Governance" }, + { id: "ch21", title: "Amazon Web Services (AWS)" }, + { id: "ch22", title: "Microsoft Azure" }, + { id: "ch23", title: "Google Cloud Platform" }, + { id: "ch24", title: "Provider Comparison & Cost Analysis" }, + { id: "ch25", title: "Docker Fundamentals" }, + { id: "ch26", title: "Container Best Practices" }, + { id: "ch27", title: "Kubernetes Basics" }, + { id: "ch28", title: "Managing Cloud Containers" }, +]; \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter0.tsx b/app/sem5/Cloud-Computing/content/chapter0.tsx new file mode 100644 index 0000000..8bbeb41 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter0.tsx @@ -0,0 +1,95 @@ +export const Ch0Content = () => ( +
+

+ Cloud Computing introduces the + infrastructure, services, and deployment models that power the modern + digital economy. This course helps you understand how cloud platforms + work, the service models used by businesses, and the architectural + principles every computing professional must know. +

+ +
+ +
+

Syllabus Overview

+
+ +
+

Unit 1: Introduction to Cloud

+
    +
  • What is Cloud Computing?
    • +
  • History and evolution of the cloud
    • +
  • Key characteristics of cloud services
    • +
  • Cloud vs traditional computing
    • +
+
+ +
+

Unit 2: Cloud Service Models

+
    +
  • Infrastructure as a Service (IaaS)
    • +
  • Platform as a Service (PaaS)
    • +
  • Software as a Service (SaaS)
    • +
  • Comparing service models
    • +
+
+ +
+

Unit 3: Deployment Models

+
    +
  • Public, Private & Hybrid Cloud
    • +
  • Community Cloud
    • +
  • Multi-cloud strategies
    • +
  • Choosing the right deployment model
    • +
+
+ +
+

Unit 4: Cloud Architecture

+
    +
  • Cloud-native architecture principles
    • +
  • Microservices and containerization
    • +
  • Scalability and load balancing
    • +
  • High availability & disaster recovery
    • +
+
+ +
+

Unit 5: Security & Compliance

+
    +
  • Identity & Access Management (IAM)
    • +
  • Data protection and encryption
    • +
  • Network security in the cloud
    • +
  • Compliance and governance
    • +
+
+ +
+

Unit 6: Cloud Platforms

+
    +
  • Amazon Web Services (AWS)
    • +
  • Microsoft Azure overview
    • +
  • Google Cloud Platform (GCP)
    • +
  • Real-world deployment scenarios
    • +
+
+ +
+
+ +
+ +
+

Prerequisites

+
+
    +
  • Basic understanding of how the internet and networks work
    • +
  • Familiarity with operating systems and file management
    • +
  • No prior cloud experience required
    • +
+
+
+
+); + +export default Ch0Content; \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter1.tsx b/app/sem5/Cloud-Computing/content/chapter1.tsx new file mode 100644 index 0000000..da2e39f --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter1.tsx @@ -0,0 +1,103 @@ +export function Ch1Content() { + return ( +
+ +

What is Cloud Computing

+ +

Cloud computing is the delivery of computing services—servers, storage, databases, + networking, software, analytics, and intelligence—over the Internet to offer faster + innovation, flexible resources, and economies of scale. Rather than owning and + maintaining physical data centers and servers, you can access technology services + on an as-needed basis from a cloud provider.

+ +

The term "cloud" refers to the Internet, and cloud computing means storing + and accessing data and programs over the Internet instead of your computer's hard drive. + It shifts computing from a product to a service, much like electricity — you use what + you need and pay accordingly.

+ +

A Brief History

+
    +
  • 1960s: John McCarthy proposed that computing could be sold as a utility, like water or electricity.
    • +
  • 1999: Salesforce pioneered delivering enterprise applications via the internet.
    • +
  • 2002: Amazon launched Amazon Web Services (AWS) offering cloud-based storage and computation.
    • +
  • 2006: AWS launched EC2 (Elastic Compute Cloud) — a major milestone in public cloud.
    • +
  • 2008: Google and Microsoft entered the cloud market with Google App Engine and Azure.
    • +
  • 2010s–present: Cloud became mainstream; hybrid and multi-cloud strategies emerged.
    • +
+ +

Key Characteristics

+

The National Institute of Standards and Technology (NIST) defines five essential characteristics of cloud computing:

+
    +
  • + On-demand self-service: Users can provision computing resources—such as server time and network storage—automatically without requiring human interaction with the service provider. For example, spinning up a virtual machine takes minutes through a web portal. +
    • +
  • + Broad network access: Cloud capabilities are available over the network and accessed through standard mechanisms — desktops, laptops, tablets, and smartphones can all connect to cloud services via the internet. +
    • +
  • + Resource pooling: The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model. Physical and virtual resources are dynamically assigned and reassigned per demand. Users generally do not control or know the exact location of the provided resources. +
    • +
  • + Rapid elasticity: Resources can be elastically provisioned and released to scale rapidly outward and inward with demand. To the consumer, the resources available appear unlimited and can be purchased in any quantity at any time. +
    • +
  • + Measured service: Cloud systems automatically control and optimize resource use through metering. Resource usage can be monitored, controlled, and reported — providing transparency for both the provider and consumer. You pay only for what you use. +
    • +
+ +

How Cloud Computing Works

+

Cloud computing relies on a front-end (client side) and back-end (server side) connected through the internet:

+
    +
  • Front-end: The client's computer or network, plus the application used to access the cloud (e.g., a web browser or app).
    • +
  • Back-end: The cloud itself — servers, computers, databases, and central servers managed by the cloud provider.
    • +
  • Network: The internet acts as the bridge between front-end and back-end.
    • +
  • Middleware: Software that allows networked computers to communicate with each other.
    • +
  • Virtualization: A core technology that allows a single physical server to act as multiple virtual machines, maximizing hardware utilization.
    • +
+ +

Why Cloud Computing Matters

+
    +
  • + Cost Efficiency: Eliminates the capital expense of buying hardware and software. You only pay for the services you use, which helps reduce operating costs, run infrastructure more efficiently, and scale as business needs change. +
    • +
  • + Scalability: Cloud services can scale up or down automatically based on usage. A startup can start small and scale to millions of users without changing their architecture. +
    • +
  • + Reliability: Major cloud providers offer 99.99% uptime SLAs with data backed up across multiple redundant sites, ensuring business continuity even during hardware failures. +
    • +
  • + Innovation Speed: Developers can provision test environments in minutes. New features and applications can be deployed globally without waiting weeks for hardware procurement. +
    • +
  • + Global Reach: Cloud providers operate data centers across the world. Applications can be deployed closer to end users to reduce latency and improve performance. +
    • +
  • + Security: Leading cloud providers invest heavily in security certifications, compliance programs, and teams of dedicated security professionals — often exceeding what most organizations can achieve on-premise. +
    • +
  • + Automatic Updates: Cloud providers handle software updates and patches, freeing IT teams to focus on business priorities rather than maintenance. +
    • +
+ +

Real-World Examples

+
    +
  • Netflix: Streams to 200+ million users worldwide using AWS cloud infrastructure.
    • +
  • Gmail / Google Drive: Store emails and documents on Google's cloud servers, accessible from any device.
    • +
  • Zoom: Runs video conferencing infrastructure on cloud platforms to handle millions of simultaneous calls.
    • +
  • Dropbox: Provides cloud-based file storage and sync across devices.
    • +
  • Swiggy / Zomato: Use cloud to handle massive traffic spikes during peak hours without maintaining dedicated servers.
    • +
+ +

Types of Cloud Users

+
    +
  • Individual Users: Use cloud for personal storage (Google Photos, iCloud), productivity (Office 365), and entertainment (Spotify, Netflix).
    • +
  • Small & Medium Businesses: Use cloud to run websites, manage CRM, and collaborate without heavy IT investment.
    • +
  • Large Enterprises: Use cloud for big data analytics, AI/ML workloads, global app deployment, and disaster recovery.
    • +
  • Government & Education: Use cloud for citizen services, e-governance platforms, and virtual learning environments.
    • +
+ +
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter10.tsx b/app/sem5/Cloud-Computing/content/chapter10.tsx new file mode 100644 index 0000000..e3f9204 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter10.tsx @@ -0,0 +1,29 @@ +export function Ch10Content() { + return ( +
+

Private Cloud

+

Infrastructure provisioned for exclusive use by a single organization, offering greater control and security.

+

Deployment Options

+
    +
  • On-Premises: Hosted in organization's own data center
    • +
  • Hosted Private Cloud: Hosted by provider but dedicated to you
    • +
  • Managed Private Cloud: Third-party manages the infrastructure
    • +
+

Advantages

+
    +
  • Complete control over security measures
    • +
  • Meet industry-specific regulatory requirements
    • +
  • Full customization of infrastructure
    • +
  • Optimized for internal workloads
    • +
+

Disadvantages

+
    +
  • High capital investment and maintenance
    • +
  • Requires skilled IT staff
    • +
  • Limited scalability by purchased capacity
    • +
+

Best For

+

Large enterprises, financial institutions, healthcare organizations, highly regulated industries.

+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter11.tsx b/app/sem5/Cloud-Computing/content/chapter11.tsx new file mode 100644 index 0000000..b9f8bf3 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter11.tsx @@ -0,0 +1,28 @@ +export function Ch11Content() { + return ( +
+

Hybrid Cloud

+

Combines public and private cloud infrastructure, allowing organizations to leverage benefits of both.

+

Key Components

+
    +
  • Private Cloud: Internal infrastructure for sensitive workloads
    • +
  • Public Cloud: External resources for variable workloads
    • +
  • Integration Layer: Seamless communication between clouds
    • +
+

Advantages

+
    +
  • Flexibility to choose best solution per workload
    • +
  • Cost optimization using public cloud for variable needs
    • +
  • Data sovereignty — keep sensitive data private
    • +
  • Burst to public cloud during peak demand
    • +
+

Use Cases

+
    +
  • Backup and disaster recovery
    • +
  • Development and testing environments
    • +
  • Variable workload handling
    • +
  • Data compliance scenarios
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter12.tsx b/app/sem5/Cloud-Computing/content/chapter12.tsx new file mode 100644 index 0000000..8d0b5c6 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter12.tsx @@ -0,0 +1,27 @@ +export function Ch12Content() { + return ( +
+

Community Cloud

+

Infrastructure shared by organizations with shared concerns, interests, or missions.

+

Examples

+
    +
  • Healthcare Community Cloud: HIPAA-compliant cloud for healthcare providers
    • +
  • Financial Community Cloud: Secure cloud for financial institutions
    • +
  • Government Community Cloud: Dedicated to government agencies
    • +
  • Research Community Cloud: For academic and research institutions
    • +
+

Advantages

+
    +
  • Reduced costs through sharing
    • +
  • Designed for specific industry compliance
    • +
  • Easy collaboration among members
    • +
+

Disadvantages

+
    +
  • Limited flexibility for specific community
    • +
  • Capacity limited to community needs
    • +
  • Dependent on community partnerships
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter13.tsx b/app/sem5/Cloud-Computing/content/chapter13.tsx new file mode 100644 index 0000000..9afae1c --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter13.tsx @@ -0,0 +1,30 @@ +export function Ch13Content() { + return ( +
+

Cloud-Native Architecture

+

Designed specifically for cloud environments, emphasizing scalability, resilience, and agility.

+

Key Principles

+
    +
  • Microservices: Break applications into small, independent services
    • +
  • Containerization: Package applications in lightweight containers
    • +
  • Orchestration: Automate deployment, scaling, and management
    • +
  • DevOps: Integrate development and operations
    • +
  • Immutable Infrastructure: Infrastructure treated as replaceable
    • +
+

Technologies

+
    +
  • Docker for containerization
    • +
  • Kubernetes for orchestration
    • +
  • Serverless / FaaS platforms
    • +
  • CI/CD pipelines
    • +
+

Design Patterns

+
    +
  • API-First: Design APIs before implementation
    • +
  • Event-Driven: Services communicate via events
    • +
  • Circuit Breaker: Prevent cascading failures
    • +
  • Database Per Service: Each service has its own database
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter14.tsx b/app/sem5/Cloud-Computing/content/chapter14.tsx new file mode 100644 index 0000000..634f080 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter14.tsx @@ -0,0 +1,36 @@ +export function Ch14Content() { + return ( +
+

Microservices Architecture

+

An architectural approach where an application is built as a collection of small, independent, loosely-coupled services.

+

Characteristics

+
    +
  • Small and Focused: Each service handles one business function
    • +
  • Independent Deployment: Deploy services without affecting others
    • +
  • Loose Coupling: Services communicate through APIs
    • +
  • Multiple Technologies: Different tech stacks per service
    • +
+

Advantages

+
    +
  • Scale individual services independently
    • +
  • Failure in one service doesn't crash entire app
    • +
  • Teams can work on services independently
    • +
  • Easier to maintain smaller codebases
    • +
+

Disadvantages

+
    +
  • Distributed system complexity
    • +
  • Data consistency challenges
    • +
  • Network latency between services
    • +
  • More services to monitor
    • +
+

Key Patterns

+
    +
  • API Gateway: Single entry point for clients
    • +
  • Service Discovery: Finding services dynamically
    • +
  • Saga Pattern: Distributed transactions
    • +
  • Strangler Pattern: Gradually replace monolith
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter15.tsx b/app/sem5/Cloud-Computing/content/chapter15.tsx new file mode 100644 index 0000000..b90b21b --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter15.tsx @@ -0,0 +1,35 @@ +export function Ch15Content() { + return ( +
+

Scalability Patterns

+

Horizontal Scaling (Scale Out)

+

Adding more servers/instances. Load distributed across multiple servers.

+
    +
  • Unlimited scalability potential
    • +
  • High availability and fault tolerance
    • +
  • More complex to manage
    • +
+

Vertical Scaling (Scale Up)

+

Adding more power (CPU, RAM) to existing servers.

+
    +
  • Simple to implement
    • +
  • Limited by hardware capabilities
    • +
  • Single point of failure
    • +
+

Auto-Scaling Strategies

+
    +
  • Metric-Based: Scale based on CPU, memory, network usage
    • +
  • Time-Based: Scale at predictable times
    • +
  • Predictive: ML to predict future needs
    • +
+

Load Balancing

+

Distributes incoming requests across multiple servers.

+
    +
  • Round-robin
    • +
  • Least connections
    • +
  • IP hash
    • +
  • Weighted distribution
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter16.tsx b/app/sem5/Cloud-Computing/content/chapter16.tsx new file mode 100644 index 0000000..7e00b96 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter16.tsx @@ -0,0 +1,45 @@ +export function Ch16Content() { + return ( +
+

High Availability & Disaster Recovery

+

Availability Tiers

+
+ + + + + + + + {[["Two Nines","99%","87.6 hours"],["Three Nines","99.9%","8.76 hours"],["Four Nines","99.99%","52.6 minutes"],["Five Nines","99.999%","5.26 minutes"]].map(([l,u,d])=>( + + + + + + ))} + +
LevelUptimeDowntime/Year
{l}{u}{d}
+
+

HA Strategies

+
    +
  • Redundancy: Duplicate critical components
    • +
  • Failover: Automatic switch to backup
    • +
  • Load Balancing: Distribute load across servers
    • +
  • Health Checks: Monitor component health
    • +
+

DR Strategies

+
    +
  • Backup and Restore: Regular backups, restore when needed
    • +
  • Pilot Light: Minimal version always running
    • +
  • Warm Standby: Ready-to-assume secondary system
    • +
  • Hot Standby: Active/active configuration
    • +
+

Key Terms

+
    +
  • RTO: Recovery Time Objective — target time to recover
    • +
  • RPO: Recovery Point Objective — maximum acceptable data loss
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter17.tsx b/app/sem5/Cloud-Computing/content/chapter17.tsx new file mode 100644 index 0000000..07281bd --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter17.tsx @@ -0,0 +1,34 @@ +export function Ch17Content() { + return ( +
+

Identity & Access Management

+

IAM controls who has access to resources and what they can do.

+

Key Concepts

+
    +
  • Authentication: Verifying user identity (who you are)
    • +
  • Authorization: Determining what user can do (permissions)
    • +
  • Accounting: Tracking user actions for audit
    • +
+

IAM Components

+
    +
  • Users: Individual identities
    • +
  • Roles: Set of permissions
    • +
  • Policies: Rules defining access
    • +
  • Groups: Collection of users with same permissions
    • +
+

MFA Types

+
    +
  • Something You Know: Password, PIN
    • +
  • Something You Have: Phone, hardware token
    • +
  • Something You Are: Biometric data
    • +
+

Best Practices

+
    +
  • Principle of Least Privilege
    • +
  • Regular Access Reviews
    • +
  • Audit Logging for all access
    • +
  • Disable unused accounts
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter18.tsx b/app/sem5/Cloud-Computing/content/chapter18.tsx new file mode 100644 index 0000000..58e56d4 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter18.tsx @@ -0,0 +1,45 @@ +export function Ch18Content() { + return ( +
+

Data Protection

+

+ Data protection in the cloud refers to the policies, tools, and processes used to safeguard data from loss, corruption, or unauthorized access throughout its lifecycle. +

+

Types of data in cloud

+
    +
  • Structured data: Databases, spreadsheets (SQL tables, CSV files)
    • +
  • Unstructured data: Emails, images, videos, documents
    • +
  • Semi-structured data: JSON, XML, logs
    • +
  • Data at rest: Stored data on disks/databases
    • +
  • Data in transit: Data moving between systems over a network
    • +
  • Data in use: Data actively being processed in memory
    • +
+

Encryption Types

+
    +
  • At Rest: All stored data is encrypted using AES-256. Even if disks are stolen, data is unreadable without the key.
    • +
  • In Transit: TLS/SSL protocols encrypt data while it moves between client and server.
    • +
  • In Use: Data actively being processed is encrypted
    • +
+

Encryption Algorithms

+
    +
  • Symmetric: Same key for encrypt/decrypt (AES, DES)
    • +
  • Asymmetric: Different keys (RSA, ECC)
    • +
  • Hashing: One-way conversion (SHA-256, MD5)
    • +
+

Data Classification

+
    +
  • Public: No restriction
    • +
  • Internal: Within organization only
    • +
  • Confidential: Limited access
    • +
  • Restricted: Highly sensitive, minimal access
    • +
+

Compliance Standards

+
    +
  • GDPR: European General Data Protection Regulation
    • +
  • HIPAA: Healthcare data protection (USA)
    • +
  • PCI DSS: Payment card data protection
    • +
  • SOC 2: Security and operational controls
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter19.tsx b/app/sem5/Cloud-Computing/content/chapter19.tsx new file mode 100644 index 0000000..fe8b4f1 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter19.tsx @@ -0,0 +1,35 @@ +export function Ch19Content() { + return ( +
+

Network Security

+

+ Network security in the cloud involves protecting the cloud infrastructure's communication channels, controlling traffic flow, and preventing unauthorized access to cloud-hosted resources. +

+

Virtual Private Cloud

+
    +
  • A logically isolated section of the cloud where you launch resources in a virtual network you define
    • +
  • You control IP address ranges, subnets, routing tables, and internet gateways
    • +
  • Resources inside a VPC are isolated from other customers' resources on the same physical hardware
    • +
  • Example: AWS VPC, Azure Virtual Network (VNet), Google VPC
    • +
+

Firewalls & Security Groups

+
    +
  • Security Groups: Virtual firewalls at the instance level. Define inbound and outbound traffic rules by port, protocol, and IP.
    • +
  • Network ACLs (Access Control Lists): Stateless firewalls at the subnet level. Control traffic entering and leaving subnets.
    • +
  • Web Application Firewall (WAF):Protects web apps from common attacks — SQL injection, cross-site scripting (XSS), DDoS at Layer 7.
    • +
+

Threat Protection

+
    +
  • DDoS Protection: Distributed Denial of Service attacks flood services with traffic to make them unavailable
    • +
  • IDS/IPS: Intrusion Detection/Prevention Systems
    • + +
+

Monitoring & Logging

+
    +
  • VPC Flow Logs: Log network flow information
    • +
  • CloudTrail: Track all API calls
    • +
  • Security Hub: Centralized security findings
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter2.tsx b/app/sem5/Cloud-Computing/content/chapter2.tsx new file mode 100644 index 0000000..c5bc6e6 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter2.tsx @@ -0,0 +1,38 @@ +export function Ch2Content() { + return ( +
+

Cloud Computing Models

+

+ Cloud computing is offered through three primary service models, each providing a different level of control, flexibility, and management. Understanding these models helps organizations choose the right approach for their needs. +

+ +

Public Cloud

+

Infrastructure provisioned for open use by the general public.

+
    +
  • Advantages: Cost-effective, scalable, no maintenance
    • +
  • Disadvantages: Less control, potential security concerns
    • +
+ +

Private Cloud

+

Infrastructure provisioned for exclusive use by one organization.

+
    +
  • Advantages: Greater control, security, customization
    • +
  • Disadvantages: Higher costs, requires dedicated staff
    • +
+ +

Hybrid Cloud

+

Composition of two or more distinct cloud infrastructures.

+
    +
  • Advantages: Flexibility, cost optimization, balance
    • +
  • Disadvantages: Complexity, integration challenges
    • +
+ +

Community Cloud

+

Infrastructure provisioned for a specific community of consumers.

+
    +
  • Advantages: Shared resources, reduced costs
    • +
  • Disadvantages: Limited scalability, niche use cases
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter20.tsx b/app/sem5/Cloud-Computing/content/chapter20.tsx new file mode 100644 index 0000000..c1e5145 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter20.tsx @@ -0,0 +1,32 @@ +export function Ch20Content() { + return ( +
+

Compliance & Governance

+

+ Cloud governance refers to the policies, controls, and processes that ensure cloud resources are used securely, efficiently, and in alignment with business and regulatory requirements. +

+

Compliance Frameworks

+
    +
  • GDPR: EU data protection — requires consent, right to be forgotten
    • +
  • HIPAA: Healthcare standard — protects patient health information
    • +
  • PCI DSS: Payment card data — encryption, regular security testing
    • +
  • SOC 2: Security/availability controls — independent audit required
    • +
  • India DPDP Act 2023:Regulates processing of digital personal data of Indian residents
    • +
  • RBI Guidelines:Reserve Bank of India mandates for financial data localization and cloud usage by banks
    • +
+

Governance Policies

+
    +
  • Password Policy: Complexity and expiration requirements
    • +
  • Access Policy: Who can access what resources
    • +
  • Encryption Policy: What data must be encrypted
    • +
  • Backup Policy: Frequency and retention rules
    • +
+

Shared Responsibility Model

+
    +
  • Provider: Infrastructure security
    • +
  • Customer: Application security and data protection
    • +
  • Shared: Access management and configuration
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter21.tsx b/app/sem5/Cloud-Computing/content/chapter21.tsx new file mode 100644 index 0000000..c23e2c5 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter21.tsx @@ -0,0 +1,39 @@ +export function Ch21Content() { + return ( +
+

Amazon Web Services (AWS)

+

+ Amazon Web Services is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Launched in 2006, AWS holds the largest market share in cloud computing. +

+ +

Compute

+
    +
  • EC2(Elastic Compute Cloud): Virtual servers in the cloud. Choose from hundreds of instance types optimized for compute, memory, storage, or GPU workloads.
    • +
  • Lambda: Serverless compute — run code without provisioning servers. Pay per execution (millisecond billing).
    • +
  • Elastic Beanstalk:PaaS-style deployment — upload your code and AWS handles provisioning, load balancing, and scaling.
    • +
  • Lightsail:Simplified VPS service for small projects, with predictable pricing.
    • +
+

Storage Services

+
    +
  • S3(Simple Storage Service): Object storage for any amount of data. Highly durable (99.999999999%). Used for backups, static website hosting, data lakes.
    • +
  • EBS(Elastic Block Store): Persistent block storage for EC2 instances (like a virtual hard disk).
    • +
  • EFS(Elastic File System): Managed NFS file storage shared across multiple EC2 instances.
    • +
  • Glacier / S3 Glacier Deep Archive: Low-cost archival storage. Retrieval takes minutes to hours.
    • +
+

Database Service

+
    +
  • RDS(Relational Database Service): Managed relational databases( Managed MySQL, PostgreSQL, Oracle, SQL Server, MariaDB.)
    • +
  • DynamoDB: Fully managed NoSQL database with single-digit millisecond latency.
    • +
  • Redshift: Petabyte-scale data warehouse for analytics.
    • +
  • Aurora: AWS's own MySQL/PostgreSQL-compatible database — 5x faster than standard MySQL.
    • +
  • ElastiCache: In-memory caching with Redis or Memcached.
    • +
+

Pricing Model

+
    +
  • On-Demand: Pay for what you use
    • +
  • Spot Instances: Up to 90% discount for spare capacity
    • +
  • Reserved Instances: Commit for 1-3 years for discount
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter22.tsx b/app/sem5/Cloud-Computing/content/chapter22.tsx new file mode 100644 index 0000000..2ccc18e --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter22.tsx @@ -0,0 +1,34 @@ +export function Ch22Content() { + return ( +
+

Microsoft Azure

+

Microsoft Azure is the second-largest cloud provider, deeply integrated with Microsoft's enterprise ecosystem (Windows Server, Active Directory, Office 365, Teams). It is the preferred choice for enterprises already running Microsoft products.

+

Compute

+
    +
  • Virtual Machines: Windows and Linux VMs
    • +
  • App Service: Web and mobile app hosting
    • +
  • Azure Functions: Serverless computing
    • +
  • AKS: Managed Kubernetes Service
    • +
+

Database

+
    +
  • SQL Database: Managed SQL Server
    • +
  • Cosmos DB: Multi-model, globally distributed NoSQL database with 99.999% SLA.
    • +
  • Azure PostgreSQL/MySQL: Managed open-source DBs
    • +
  • Azure Synapse Analytics: Unified analytics service combining data warehousing and big data.
    • +
+

Enterprise Integration

+
    +
  • Active Directory integration
    • +
  • Office 365 / Microsoft 365 seamless integration
    • +
  • Strong hybrid cloud capabilities
    • +
+

AI/ML Services

+
    +
  • Azure AI — pre-built models
    • +
  • Azure Machine Learning — custom models
    • +
  • Cognitive Services — vision, speech, language
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter23.tsx b/app/sem5/Cloud-Computing/content/chapter23.tsx new file mode 100644 index 0000000..f3e968c --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter23.tsx @@ -0,0 +1,45 @@ +export function Ch23Content() { + return ( +
+

Google Cloud Platform (GCP)

+

Google Cloud Platform is the third-largest cloud provider, known for its leadership in data analytics, machine learning, and Kubernetes (which Google invented). It powers Google Search, YouTube, and Gmail — demonstrating extreme scale and reliability.

+

Compute

+
    +
  • Compute Engine:IaaS VMs with custom machine types. Sustained use discounts automatically applied.
    • +
  • App Engine: Fully managed PaaS. Zero server management.
    • +
  • Cloud Run: Run containerized apps in a fully serverless environment. Scales to zero.
    • +
  • GKE(Google Kubernetes Engine):The most mature managed Kubernetes service — GCP invented Kubernetes.
    • +
+

Storage

+
    +
  • Cloud Storage:Object storage with four classes — Standard, Nearline, Coldline, Archive — optimized for different access frequencies.
    • +
  • Persistent Disk / Hyperdisk:Block storage for Compute Engine VMs.
    • +
  • Filestore: Managed NFS file storage.
    • +
+

Database

+
    +
  • Cloud SQL: Managed MySQL, PostgreSQL, and SQL Server.
    • +
  • Cloud Spanner: Globally distributed, horizontally scalable relational database — unique to GCP. Combines ACID transactions with global scale.
    • +
  • Firestore / Datastore: Serverless NoSQL document database for mobile and web apps.
    • +
  • Bigtable: Petabyte-scale NoSQL for time-series, IoT, and analytics workloads. Powers Google Search internally
    • +
+

Data Analytics

+
    +
  • BigQuery: Data warehouse for large-scale analytics
    • +
  • Dataflow: Data pipeline processing
    • +
  • Pub/Sub: Real-time messaging
    • +
+

Machine Learning

+
    +
  • Vertex AI: Unified ML platform
    • +
  • TensorFlow: Open-source ML framework
    • +
+

Unique Advantages

+
    +
  • Best-in-class BigQuery analytics
    • +
  • Strong ML/AI capabilities
    • +
  • Competitive pricing with no upfront commitment
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter24.tsx b/app/sem5/Cloud-Computing/content/chapter24.tsx new file mode 100644 index 0000000..2a4ebe4 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter24.tsx @@ -0,0 +1,48 @@ +export function Ch24Content() { + return ( +
+

Provider Comparison & Cost Analysis

+
+ + + + + + + + + {[ + ["Maturity","Most mature (2006)","Strong enterprise","Growing fast"], + ["Services","200+ services","180+ services","150+ services"], + ["Best For","Enterprises","Microsoft shops","Data/ML teams"], + ["Pricing","Pay-as-you-go","Pay-as-you-go","Pay-as-you-go"], + ].map(([f,a,az,g])=>( + + + + + + + ))} + +
FactorAWSAzureGCP
{f}{a}{az}{g}
+
+

Pricing Models

+
    +
  • On-demand / Pay-as-you-go:Pay per second/minute/hour of use. No commitment. Highest unit price.
    • +
  • Reserved Instances (AWS) / Reserved Capacity (Azure) / Committed Use (GCP): 1 or 3 year commitment — up to 72% discount vs on-demand.
    • +
  • Spot Instances (AWS) / Spot VMs (Azure) / Preemptible VMs (GCP): Use spare capacity at 60–90% discount. Can be interrupted with short notice. Ideal for batch jobs, ML training.
    • +
  • Savings Plans (AWS):Flexible pricing based on consistent usage amount, not specific instance types.
    • +
  • Free Tiers: All three providers offer free tiers — AWS Free Tier (12 months), Azure Free Tier, GCP Always Free tier.
    • +
+

Cost Optimization Strategies

+
    +
  • Right Sizing: Use appropriate instance sizes
    • +
  • Reserved Instances: Commit for 1-3 years for discount
    • +
  • Spot/Preemptible: Use spare capacity for non-critical work
    • +
  • Auto-Scaling: Scale down when not needed
    • +
  • Storage Optimization: Use appropriate storage tiers
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter25.tsx b/app/sem5/Cloud-Computing/content/chapter25.tsx new file mode 100644 index 0000000..e83fbb2 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter25.tsx @@ -0,0 +1,38 @@ +export function Ch25Content() { + return ( +
+

Docker Fundamentals

+

Docker is an open-source platform that automates the deployment of applications inside lightweight, portable containers. It revolutionized software delivery by ensuring "it works on my machine" is never an excuse — containers run identically everywhere.

+

The problem Docker Solves

+
    +
  • Traditional deployment: Install OS → install runtime → install dependencies → deploy app. Conflicts arise between different apps' dependencies.
    • +
  • "Works on my machine" problem: Dev, staging, and production environments differ.
    • +
  • Docker solution: Package the application with all its dependencies into a single container image.
    • +
+

Docker Architecture

+
    +
  • Docker Client: Command-line interface
    • +
  • Docker Daemon: Background service managing containers
    • +
  • Docker Image:A read-only template used to create containers. Layers of filesystem changes stacked on top of a base image.
    • +
  • Docker Container: A running instance of an image. Lightweight, isolated process sharing the host OS kernel. Much faster and lighter than a VM.
    • +
  • Docker file:Text file with instructions to build a Docker image. Every instruction creates a new layer.
    • +
  • Docker Registry: Repository for images (e.g. Docker Hub)
    • +
+

Sample Dockerfile

+ 
{`FROM python:3.9
+WORKDIR /app
+COPY requirements.txt .
+RUN pip install -r requirements.txt
+COPY . .
+CMD ["python", "app.py"]`}
+

Common Commands

+
    +
  • docker build: Build image from Dockerfile
    • +
  • docker run: Start a container
    • +
  • docker ps: List running containers
    • +
  • docker stop: Stop a container
    • +
  • docker logs: View container logs
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter26.tsx b/app/sem5/Cloud-Computing/content/chapter26.tsx new file mode 100644 index 0000000..a1c7866 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter26.tsx @@ -0,0 +1,46 @@ +export function Ch26Content() { + return ( +
+

Container Best Practices

+

Image Best Practices

+
    +
  • Use official base images from Docker Hub — they are regularly updated and security-patched
    • +
  • Use specific image tags (e.g., node:18.17.1-alpine) never latest in production — ensures reproducibility
    • +
  • Use minimal base images (Alpine Linux ~5MB vs Ubuntu ~70MB) to reduce attack surface and image size
    • +
  • Order Dockerfile instructions for cache efficiency
    • +
  • Never store secrets (API keys, passwords) in images. Use environment variables or secrets managers.
    • +
  • Scan images for vulnerabilities using tools like Trivy, Snyk, or Docker Scout before deployment
    • +
+

Security Best Practices

+
    +
  • Never run containers as root user
    • +
  • Scan images regularly for vulnerabilities
    • +
  • Keep base images updated
    • +
  • Use secrets managers, not environment variables for sensitive data
    • +
  • Network policies: Limit which containers can talk to each other
    • +
  • Set resource limits (CPU, memory) to prevent a single container from starving others
    • +
+ +

CI/CD Pipeline for Containers

+
    +
  • Developer pushes code to Git repository.
    • +
  • CI system (GitHub Actions, Jenkins, GitLab CI) automatically builds Docker image
    • +
  • Image is scanned for vulnerabilities
    • +
  • Image pushed to container registry (ECR, ACR, GCR, Docker Hub)
    • +
  • CD system (ArgoCD, Flux, Spinnaker) deploys new image to Kubernetes cluster
    • +
  • Automated tests run against deployed service
    • +
  • Rollback automatically triggered if health checks fail
    • +
+

Runtime Best Practices

+
    +
  • Set CPU and memory resource limits
    • +
  • Send logs to stdout/stderr
    • +
  • Use .dockerignore to exclude unnecessary files
    • +
  • Treat containers as ephemeral (non-persistent)
    • +
+

Health Check Example

+ 
{`HEALTHCHECK --interval=30s --timeout=10s --retries=3 \\
+  CMD curl -f http://localhost:3000/health || exit 1`}
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter27.tsx b/app/sem5/Cloud-Computing/content/chapter27.tsx new file mode 100644 index 0000000..f3ead56 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter27.tsx @@ -0,0 +1,52 @@ +export function Ch27Content() { + return ( +
+

Kubernetes Basics

+

Kubernetes (K8s) is an open-source container orchestration platform originally developed by Google, now maintained by the CNCF. It automates deployment, scaling, and management of containerized applications across clusters of machines.

+ +

Why Kubernetes?

+

Running one container on one machine is easy. Running hundreds of containers across dozens of machines, ensuring they're healthy, restarting failed ones, load balancing traffic, and rolling out updates without downtime — that's Kubernetes' job.

+ +

Architecture

+
    +
  • Master Node: Controls the cluster
    • +
  • Worker Nodes: Run the containers
    • +
  • etcd: Distributed key-value store for cluster state
    • +
  • API Server: RESTful interface to the cluster
    • +
+

Key Objects

+
    +
  • Pod: Smallest deployable unit (one or more containers)
    • +
  • Deployment: Manages replica pods declaratively
    • +
  • Service: Network access to pods
    • +
  • Namespace: Virtual cluster for resource isolation
    • +
  • ConfigMap/Secret: Configuration and sensitive data
    • +
+

Sample Manifest

+ 
{`apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: web-app
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: web
+  template:
+    spec:
+      containers:
+      - name: app
+        image: myapp:1.0
+        ports:
+        - containerPort: 8080`}
+

kubectl Commands

+
    +
  • kubectl apply -f deployment.yaml
    • +
  • kubectl get pods
    • +
  • kubectl describe pod <name>
    • +
  • kubectl logs <pod-name>
    • +
  • kubectl scale deployment <name> --replicas=5
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter28.tsx b/app/sem5/Cloud-Computing/content/chapter28.tsx new file mode 100644 index 0000000..eeb2bb3 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter28.tsx @@ -0,0 +1,37 @@ +export function Ch28Content() { + return ( +
+

Managing Cloud Containers

+

Container Lifecycle

+
    +
  • Build → Push → Pull → Run → Monitor → Update → Delete
    • +
+

Container Registries

+
    +
  • Docker Hub: Public registry
    • +
  • Amazon ECR: AWS container registry
    • +
  • Azure Container Registry
    • +
  • Google Container Registry
    • +
+

Deployment Strategies

+
    +
  • Rolling: Gradual replacement of old with new
    • +
  • Blue-Green: Two identical environments, switch traffic
    • +
  • Canary: Test new version with subset of users
    • +
+

Scaling Strategies

+
    +
  • HPA: Horizontal Pod Autoscaling based on metrics
    • +
  • Cluster Autoscaler: Add/remove nodes automatically
    • +
  • Set resource requests and limits to prevent abuse
    • +
+

Security

+
    +
  • Runtime security monitoring
    • +
  • Vulnerability scanning of images
    • +
  • RBAC in Kubernetes
    • +
  • Network segmentation with namespaces
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter3.tsx b/app/sem5/Cloud-Computing/content/chapter3.tsx new file mode 100644 index 0000000..a184ad0 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter3.tsx @@ -0,0 +1,30 @@ +export function Ch3Content() { + return ( +
+

Benefits and Challenges

+ +

Benefits of Cloud Computing

+
    +
  • Cost Savings: No upfront capital expenditure on hardware. Pay-as-you-go pricing reduces waste.
    • +
  • Scalability: Automatically adjust resources based on demand.
    • +
  • Reliability: Built-in redundancy, automatic failover, disaster recovery.
    • +
  • Performance: Access to cutting-edge hardware without maintenance burden.
    • +
  • Security: Professional-grade security infrastructure.
    • +
  • Flexibility: Choose from various service and deployment models.
    • +
  • Accessibility: Access services from anywhere with internet.
    • +
+ +

Challenges of Cloud Computing

+
    +
  • Security and Privacy: Storing sensitive data on third-party servers raises concerns about breaches, unauthorized access, and compliance.
    • +
  • Vendor Lock-in: Migrating from one cloud provider to another is complex and expensive. Proprietary services tie organizations to one vendor.
    • +
  • Network Dependency: Complete reliance on internet connectivity.
    • +
  • Performance Variability: Potential latency for real-time applications.
    • +
  • Compliance Issues: Regulated industries (healthcare, banking) must ensure cloud providers meet legal standards like HIPAA, GDPR, RBI guidelines.
    • +
  • Cost Management: Unexpected charges if resources not monitored.
    • +
  • Latency: For real-time applications, network delays between user and cloud data center can be a problem..
    • + +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter4.tsx b/app/sem5/Cloud-Computing/content/chapter4.tsx new file mode 100644 index 0000000..be6205c --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter4.tsx @@ -0,0 +1,55 @@ +export function Ch4Content() { + return ( +
+

Cloud vs On-Premises

+ +

Comparison

+
+ + + + + + + + + + {[ + ["Capital Investment", "Low (pay-as-you-go)", "High upfront"], + ["Maintenance", "Provider responsible", "Your responsibility"], + ["Scalability", "High and automatic", "Limited, needs hardware"], + ["Security", "Shared responsibility", "Your responsibility"], + ["Latency", "Network dependent", "Local and fast"], + ["Customization", "Limited", "Full control"], + ["Time to Deploy", "Fast", "Slow"], + ].map(([f, c, o]) => ( + + + + + + ))} + +
FactorCloudOn-Premises
{f}{c}{o}
+
+ +

When to Choose Cloud

+
    +
  • Need flexibility and scalability
    • +
  • Lower upfront costs important
    • +
  • Focus on core business
    • +
  • Need global reach
    • +
  • Rapid deployment required
    • +
+ +

When to Choose On-Premises

+
    +
  • Maximum control needed
    • +
  • Low latency requirements critical
    • +
  • Sensitive data security
    • +
  • Compliance with specific regulations
    • +
  • Predictable, stable workloads
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter5.tsx b/app/sem5/Cloud-Computing/content/chapter5.tsx new file mode 100644 index 0000000..7a87665 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter5.tsx @@ -0,0 +1,39 @@ +export function Ch5Content() { + return ( +
+

Infrastructure as a Service (IaaS)

+

IaaS provides virtualized computing resources over the internet. You rent IT infrastructure instead of buying and maintaining it.

+ +

Core Components

+
    +
  • Compute: Virtual machines with customizable CPU, RAM, storage
    • +
  • Storage: Object storage, block storage, file storage
    • +
  • Networking: Virtual networks, load balancers, firewalls, VPNs
    • +
  • Databases: Managed database services (MySQL, PostgreSQL, NoSQL)
    • +
+ +

Key Benefits

+
    +
  • Flexibility: Scale resources up or down as needed
    • +
  • Cost-Effective: No capital investment in hardware
    • +
  • Reliability: Built-in redundancy and backups
    • +
  • Performance: Enterprise-grade infrastructure
    • +
+ +

Examples

+
    +
  • AWS: EC2, S3, RDS
    • +
  • Microsoft Azure Virtual Machines
    • +
  • Google Cloud Compute Engine
    • +
+ +

Use Cases

+
    +
  • Web application hosting
    • +
  • Development and test environments
    • +
  • High-performance computing
    • +
  • Big data analysis
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter6.tsx b/app/sem5/Cloud-Computing/content/chapter6.tsx new file mode 100644 index 0000000..1d9ea4d --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter6.tsx @@ -0,0 +1,34 @@ +export function Ch6Content() { + return ( +
+

Platform as a Service (PaaS)

+

PaaS provides a platform for developing, testing, and deploying applications without managing underlying infrastructure.

+ +

Key Features

+
    +
  • Development Tools: IDEs, compilers, debuggers, version control
    • +
  • Database Management: Built-in database services
    • +
  • Application Server: Ready-to-use runtime environment
    • +
  • Middleware: Pre-built integration services
    • +
  • Security: Built-in authentication and authorization
    • +
+ +

Benefits

+
    +
  • Faster Development: Pre-built components accelerate development
    • +
  • Reduced Complexity: No infrastructure management needed
    • +
  • Cost Savings: No hardware investment
    • +
  • Automatic Updates: Platform updates managed by provider
    • +
+ +

Limitations

+
    +
  • Vendor Dependency: Limited control over platform features
    • +
  • Performance Constraints: Limited customization options
    • +
+ +

Examples

+

Heroku, Google App Engine, AWS Elastic Beanstalk, Azure App Service

+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter7.tsx b/app/sem5/Cloud-Computing/content/chapter7.tsx new file mode 100644 index 0000000..fd10937 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter7.tsx @@ -0,0 +1,32 @@ +export function Ch7Content() { + return ( +
+

Software as a Service (SaaS)

+

SaaS delivers software applications over the internet, accessed via web browsers. No installation or maintenance required.

+ +

Characteristics

+
    +
  • Web-Based Access: Use browser to access applications
    • +
  • Automatic Updates: Provider manages all updates
    • +
  • Multi-Tenant: Multiple users share the same instance
    • +
  • Data Accessibility: Access data from anywhere
    • +
+ +

Popular SaaS Applications

+
    +
  • Productivity: Google Workspace, Microsoft 365, Slack
    • +
  • Collaboration: Trello, Asana, Monday.com
    • +
  • Communication: Zoom, Microsoft Teams
    • +
  • CRM: Salesforce
    • +
  • Analytics: Tableau, Looker
    • +
+ +

Limitations

+
    +
  • Limited Customization: Features determined by provider
    • +
  • Data Security: Data stored on provider's servers
    • +
  • Internet Dependency: Requires stable internet connection
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter8.tsx b/app/sem5/Cloud-Computing/content/chapter8.tsx new file mode 100644 index 0000000..68227a5 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter8.tsx @@ -0,0 +1,43 @@ +export function Ch8Content() { + return ( +
+

Comparing Service Models

+ +
+ + + + + + + + + + + {[ + ["You Manage", "App, Data, Runtime, OS", "App, Data", "Data only"], + ["Provider Manages", "Virtualization, Hardware", "Runtime, OS, Hardware", "Everything"], + ["Examples", "AWS EC2, Azure VMs", "Heroku, App Engine", "Google Workspace, Salesforce"], + ["Best For", "Max control", "Rapid development", "Ready-made apps"], + ].map(([a, i, p, s]) => ( + + + + + + + ))} + +
AspectIaaSPaaSSaaS
{a}{i}{p}{s}
+
+ +

Serverless Computing

+

Emerging model where developers write code without managing servers.

+
    +
  • Examples: AWS Lambda, Google Cloud Functions
    • +
  • Pay only for actual execution time
    • +
  • Also known as Functions as a Service (FaaS)
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/content/chapter9.tsx b/app/sem5/Cloud-Computing/content/chapter9.tsx new file mode 100644 index 0000000..aedb1a8 --- /dev/null +++ b/app/sem5/Cloud-Computing/content/chapter9.tsx @@ -0,0 +1,28 @@ +export function Ch9Content() { + return ( +
+

Public Cloud

+

Infrastructure provisioned for open use by the general public, owned by a cloud provider.

+

Major Providers

+
    +
  • AWS: Most popular, comprehensive services
    • +
  • Microsoft Azure: Strong enterprise integration
    • +
  • Google Cloud (GCP): Excellent data analytics
    • +
+

Advantages

+
    +
  • No upfront capital investment
    • +
  • Unlimited scalability
    • +
  • High reliability with built-in redundancy
    • +
  • Access from anywhere globally
    • +
+

Disadvantages

+
    +
  • Limited control and customization
    • +
  • Security concerns with shared infrastructure
    • +
  • Vendor lock-in risk
    • +
  • Compliance challenges
    • +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/layout.tsx b/app/sem5/Cloud-Computing/layout.tsx new file mode 100644 index 0000000..380f91d --- /dev/null +++ b/app/sem5/Cloud-Computing/layout.tsx @@ -0,0 +1,16 @@ +import Sidebar from "./components/sidebar"; + +export default function CloudComputingLayout({ + children, +}: { + children: React.ReactNode; +}) { + return ( +
+ +
+ {children} +
+
+ ); +} \ No newline at end of file diff --git a/app/sem5/Cloud-Computing/page.jsx b/app/sem5/Cloud-Computing/page.jsx new file mode 100644 index 0000000..e387b95 --- /dev/null +++ b/app/sem5/Cloud-Computing/page.jsx @@ -0,0 +1,147 @@ +'use client'; + +import { cloudComputingCourse } from '@/lib/course/CloudComputing'; +import Link from 'next/link'; +import { useState } from 'react'; + +export default function CloudComputingCourse() { + const [expandedUnit, setExpandedUnit] = useState(null); + const course = cloudComputingCourse; + + return ( +
+ {/* Header */} +
+
+
+ {course.icon} +
+

{course.title}

+

{course.description}

+
+
+ + ← Back + +
+
+ +
+ {/* Welcome Section */} +
+

Welcome to Cloud Computing

+

+ This comprehensive course covers the theory and practice of cloud computing, including infrastructure services, + platform services, deployment models, and major cloud providers like AWS, Azure, and GCP. You'll learn + how to design scalable applications, manage containerized workloads, secure cloud resources, and implement + cloud-native architectures. +

+
+
+

Total Units

+

{course.units.length}

+
+
+

Total Chapters

+

28

+
+
+

Difficulty

+

Beginner → Advanced

+
+
+
+ + {/* Units Grid */} +
+

Course Curriculum

+
+ {course.units.map((unit) => ( +
+ + + {expandedUnit === unit.id && ( +
+ {/* Topics */} +
+

Topics covered:

+
    + {unit.topics.map((topic, idx) => ( +
  • + • + {topic} +
    • + ))} +
+
+ + {/* Chapters */} +
+

Chapters:

+
    + {unit.chapters.map((chapter) => ( +
  • + + ➜ Chapter {chapter.id}: {chapter.title} + +
    • + ))} +
+
+
+ )} +
+ ))} +
+
+ + {/* Syllabus Topics */} +
+

Complete Syllabus Overview

+
+
+

Fundamentals

+
    +
  • ✓ Cloud computing concepts and characteristics
    • +
  • ✓ Service models: IaaS, PaaS, SaaS
    • +
  • ✓ Deployment models: Public, Private, Hybrid
    • +
  • ✓ Benefits and challenges
    • +
  • ✓ Cloud vs On-premises comparison
    • +
+
+
+

Advanced Topics

+
    +
  • ✓ Cloud architecture and design patterns
    • +
  • ✓ Security and compliance (IAM, encryption, GDPR)
    • +
  • ✓ Major providers: AWS, Azure, GCP
    • +
  • ✓ Containerization with Docker
    • +
  • ✓ Orchestration with Kubernetes
    • +
+
+
+
+
+
+ ); +} \ No newline at end of file diff --git a/lib/course/CloudComputing.js b/lib/course/CloudComputing.js new file mode 100644 index 0000000..de8f364 --- /dev/null +++ b/lib/course/CloudComputing.js @@ -0,0 +1,138 @@ +export const cloudComputingCourse = { + id: 'cloud-computing', + title: 'Cloud Computing', + description: 'Master cloud computing fundamentals, deployment models, and major cloud providers like AWS, Azure, and GCP', + category: 'Cloud & DevOps', + semester: 5, + status: 'published', + icon: '☁️', + color: '#3b82f6', + + units: [ + { + id: 1, + title: 'Introduction to Cloud Computing', + chapters: [ + { id: 1, title: 'What is Cloud Computing' }, + { id: 2, title: 'Cloud Computing Models' }, + { id: 3, title: 'Benefits and Challenges' }, + { id: 4, title: 'Cloud vs On-Premises' } + ], + topics: [ + 'Definition and key characteristics', + 'On-demand self-service', + 'Broad network access', + 'Resource pooling', + 'Rapid elasticity', + 'Measured service', + 'Cost-benefit analysis' + ] + }, + { + id: 2, + title: 'Cloud Service Models', + chapters: [ + { id: 5, title: 'Infrastructure as a Service (IaaS)' }, + { id: 6, title: 'Platform as a Service (PaaS)' }, + { id: 7, title: 'Software as a Service (SaaS)' }, + { id: 8, title: 'Comparing Service Models' } + ], + topics: [ + 'IaaS: Compute, Storage, Networking', + 'PaaS: Development environments and tools', + 'SaaS: Applications and benefits', + 'Serverless computing (Functions as a Service)', + 'Choosing the right model for your use case' + ] + }, + { + id: 3, + title: 'Cloud Deployment Models', + chapters: [ + { id: 9, title: 'Public Cloud' }, + { id: 10, title: 'Private Cloud' }, + { id: 11, title: 'Hybrid Cloud' }, + { id: 12, title: 'Community Cloud' } + ], + topics: [ + 'Public cloud architecture and access', + 'Private cloud ownership and control', + 'Hybrid cloud integration strategies', + 'Community cloud for specific industries', + 'Deployment model comparison matrix' + ] + }, + { + id: 4, + title: 'Cloud Architecture & Design', + chapters: [ + { id: 13, title: 'Cloud-Native Architecture' }, + { id: 14, title: 'Microservices Architecture' }, + { id: 15, title: 'Scalability Patterns' }, + { id: 16, title: 'High Availability & Disaster Recovery' } + ], + topics: [ + 'Cloud-native design principles', + 'Breaking monoliths into microservices', + 'Horizontal vs vertical scaling', + 'Load balancing strategies', + 'Multi-region and multi-zone deployment', + 'Fault tolerance and resilience' + ] + }, + { + id: 5, + title: 'Cloud Security & Compliance', + chapters: [ + { id: 17, title: 'Identity & Access Management' }, + { id: 18, title: 'Data Protection' }, + { id: 19, title: 'Network Security' }, + { id: 20, title: 'Compliance & Governance' } + ], + topics: [ + 'IAM roles, policies, and access control', + 'Multi-factor authentication', + 'Encryption at rest and in transit', + 'VPCs, security groups, and firewalls', + 'GDPR, HIPAA, SOC 2 compliance', + 'Cloud audit and monitoring' + ] + }, + { + id: 6, + title: 'Major Cloud Providers', + chapters: [ + { id: 21, title: 'Amazon Web Services (AWS)' }, + { id: 22, title: 'Microsoft Azure' }, + { id: 23, title: 'Google Cloud Platform' }, + { id: 24, title: 'Provider Comparison & Cost Analysis' } + ], + topics: [ + 'AWS: EC2, S3, RDS, Lambda', + 'Azure: VMs, App Service, Cosmos DB', + 'GCP: Compute Engine, Cloud Storage, BigQuery', + 'Cost estimation and optimization', + 'Multi-cloud strategies', + 'Vendor lock-in considerations' + ] + }, + { + id: 7, + title: 'Containerization & Orchestration', + chapters: [ + { id: 25, title: 'Docker Fundamentals' }, + { id: 26, title: 'Container Best Practices' }, + { id: 27, title: 'Kubernetes Basics' }, + { id: 28, title: 'Managing Cloud Containers' } + ], + topics: [ + 'Docker images, containers, and registries', + 'Container optimization and security', + 'Kubernetes architecture and concepts', + 'Pods, services, and deployments', + 'Container networking and storage', + 'Container orchestration at scale' + ] + } + ] +}; \ No newline at end of file