DevOps syllabus

PEC-361A-IT · Third Year Information Technology, SPPU 2024 pattern. Every unit, the marks scheme, course outcomes and books, copied from the official syllabus PDF.

PEC-361A-IT3 h/week theoryCCE 30 + End-sem 70
45hours of theory
05.units
03.credits

Unit-wise syllabus

UNIT I

Introduction To Devops And The Culture.

9 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • What is DevOps, DevOps culture, collaboration, automation, and Agile connection, Highlevel DevOps lifecycle and pipeline phases, Roles of developer, operations, and DevOps engineer.
  • Case Study : Improving Collaboration in an E-Commerce Startup
Preserved official unit paragraph

What is DevOps, DevOps culture, collaboration, automation, and Agile connection, Highlevel DevOps lifecycle and pipeline phases, Roles of developer, operations, and DevOps engineer. Case Study : Improving Collaboration in an E-Commerce Startup

Unit permalink
UNIT II

Microservices Architecture And Cloud Native Development.

9 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Monolithic vs. Microservices architecture, Benefits and challenges of microservices, Containerization principles, Introduction to Docker: image, container, Dockerfile, Orchestration vs. automation.
  • Case Study: Migrating from Monolithic to Microservices
Preserved official unit paragraph

Monolithic vs. Microservices architecture, Benefits and challenges of microservices, Containerization principles, Introduction to Docker: image, container, Dockerfile, Orchestration vs. automation. Case Study: Migrating from Monolithic to Microservices

Unit permalink
UNIT III

Continuous Integration And Test-Driven Development.

9 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Why CI/CD is used: faster feedback and quality, Code repository and CI server concepts, CI vs. CD, Basic CI/CD pipeline stages, Simple pipeline examples and reports.
  • Case Study: Automating Software Builds
Preserved official unit paragraph

Why CI/CD is used: faster feedback and quality, Code repository and CI server concepts, CI vs. CD, Basic CI/CD pipeline stages, Simple pipeline examples and reports. Case Study: Automating Software Builds

Unit permalink
UNIT IV

Continuous Deployment And Orchestration.

9 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Continuous Deployment: idea and benefits/risks, Deployment pipeline overview, Basic testing stages: unit, integration, smoke/acceptance, Release readiness and rollback awareness.
  • Case Study: Reducing Production Bugs through Automated Testing
Preserved official unit paragraph

Continuous Deployment: idea and benefits/risks, Deployment pipeline overview, Basic testing stages: unit, integration, smoke/acceptance, Release readiness and rollback awareness. Case Study: Reducing Production Bugs through Automated Testing

Unit permalink
UNIT V

Continuous Monitoring And Site Reliability.

9 hours

Derived reading outline. Source text split at semicolons, line breaks and sentence boundaries, not an official topic hierarchy.

  • Why monitoring matters, Logs, metrics, dashboards, White-box vs. Black-box monitoring, What is SRE? How SRE relates to DevOps, Tool awareness: Git, Docker, Jenkins, Ansible, Selenium, Prometheus, Jira, ELK Stack.
  • Case Study: Ensuring High Availability of a Streaming Platform
Preserved official unit paragraph

Why monitoring matters, Logs, metrics, dashboards, White-box vs. Black-box monitoring, What is SRE? How SRE relates to DevOps, Tool awareness: Git, Docker, Jenkins, Ansible, Selenium, Prometheus, Jira, ELK Stack. Case Study: Ensuring High Availability of a Streaming Platform

Unit permalink

Marks and credits

HeadMarksCredit
CCE (continuous comprehensive evaluation)303
End-semester exam70

Prerequisite: Software Engineering.

Course outcomes

  1. CO1Understand the fundamental concepts, culture, principles, and practices of DevOps.
  2. CO2Explain microservices architecture, cloud-native development, containerization, and orchestration technologies used in DevOps environments.
  3. CO3Comprehend and implement Continuous Integration (CI) and Continuous Delivery (CD) concepts, strategies, and pipelines.
  4. CO4Analyze and compare various stages of Continuous Deployment, testing strategies, and deployment pipeline practices.
  5. CO5Evaluate monitoring systems, Site Reliability Engineering (SRE) practices, and apply modern DevOps tools such as Git, Docker, Kubernetes, Jenkins, Ansible, Selenium, Prometheus, Jira, and ELK Stack in software development and operations.

Books

Text books

Reference books

FAQ

How many units are in DevOps?

DevOps (PEC-361A-IT) has 5 units and 45 hours of theory: Unit I Introduction To Devops And The Culture. (9 h); Unit II Microservices Architecture And Cloud Native Development. (9 h); Unit III Continuous Integration And Test-Driven Development. (9 h); Unit IV Continuous Deployment And Orchestration. (9 h); Unit V Continuous Monitoring And Site Reliability. (9 h).

What is the marks scheme for DevOps?

The official Information Technology 2024 pattern syllabus lists continuous comprehensive evaluation (CCE) for 30 marks and the end-semester exam for 70 marks, for 3 credits.

What should I know before DevOps?

Prerequisite listed in the syllabus: Software Engineering.

Add to my plan

Browse all syllabus courses