TheAltF4Stream
Introducing DevOps for Developers
4 hours, 42 minutes
CC
Course Description
Take your first steps into DevOps guided from the perspective of a developer! You’ll improve software teams’ ability to build and ship software reliably through automation and monitoring. Learn to use Technical Design Documents, standardize infrastructure with Pulumi, and automate S3 buckets and services. Experience live-coding a CLI tool, implementing Dockerfiles, and integrating CircleCI. Discover if DevOps is the right fit for you!
This course and others like it are available as part of our Frontend Masters video subscription.
Preview
CloseWhat They're Saying
Erik Reinert's DevOps course was really an eye-opener for me; I didn't know until now that there are tools to automate infrastructure, that DevOps is exciting, and that there's a new path for me to learn more about it.
Marc Espiritu
Marc Espiritu
I completed both Introducing DevOps for Developers and Enterprise Cloud Infrastructure and I must say I loved the content. Instead of just giving you info that you could find via reading docs, it teaches you a mindset. This is priceless.
Andrea Bertanzon
andreabertanzon
Learn Straight from the Experts Who Shape the Modern Web
Your Path to Senior Developer and Beyond
- 200+ In-depth courses
- 18 Learning Paths
- Industry Leading Experts
- Live Interactive Workshops
Table of Contents
Introduction
Section Duration: 44 minutes
Erik Reinert introduces the course by providing social media links and some professional background. A student's question regarding if Erik would recommend DevOps for someone entering the tech field and a discussion regarding beneficial experience for a career in DevOps are also covered in this segment.
Erik briefly discusses the course structure and what currently exists for definitions, culture challenges, communication, and suboptimal solutions regarding DevOps.
Erik discusses the goals of DevOps, how it approaches realizing them through technology and communication, and what DevOps is not. Student questions regarding handling companies differing opinions of DevOps and the difference between companies putting their spin on DevOps and defining your DevOps are also covered in this segment.
Erik demonstrates identifying the why, what, and who of a problem. Identifying these helps provide the end goal and a clear understanding of the strategy to achieve that goal.
Erik discusses DevOps standards: guidelines or best practices that typically cover communication, collaboration, and automation. Examples of automation, planning, quality, and communication standards are provided in this segment.
Technical Design Documents
Section Duration: 1 hour, 5 minutes
Erik demonstrates the benefits of technical design documents, including guiding software system development and communicating technical aspects to stakeholders and developers. Suggestions for how to approach your first technical design document are also provided in this segment.
Erik walks through an example technical design document and provides recommendations for how to provide clear and concise information.
Erik walks through creating a problem statement and identifying currently used communication methods for a student provided technical design document prompt.
Erik walks through deciding which communication methods are preferred and condenses where information is located. Documenting culture standards to assist with organization is also covered in this segment.
Erik discusses addressing possible pain-points of a technical design document's suggested changes.
Erik demonstrates providing proposed solutions in a technical design document. Steps to take after the first draft of the document is finished are also discussed in this segment.
Managing Infrastructure with Pulumi
Section Duration: 1 hour, 45 minutes
Erik discusses identifying the problems of and creating technical design documents regarding standardizing infrastructure and CI/CD. A technical design document is created for standardizing infrastructure in the segment.
Erik demonstrates utilizing the previously created technical design document to build a service directory to manage and update resources. A brief walk through of setup instructions and a brief overview of Pulumi are also covered in this segment.
Erik walks through setting up a new Pulumi project including, defining and accessing stack instances, and deploying the stack. A demonstration of the files generated by Pulumi is also covered in this segment.
Erik demonstrates creating Components by extending Pulumi's ComponentResource class to create a new class component. A discussion regarding the results of Pulumi initially bridging Terraform providers to Pulumi is also covered in this segment.
Erik discusses standardizing and automating buckets by creating an interface for standard bucket arguments and access restrictions. A demonstration of Pulumi options is also covered in this segment.
Erik walks through how to generate buckets by creating a DevOps bucket resource. Properly scoping the bucket ensures isolation of resources.
Erik demonstrates expanding bucket automation for large scale applications.
Erik walks through creating and standardizing a frontend service to be utilized by the standardized buckets. Creating new buckets that utilize the frontend service is also covered in this segment.
Erik demonstrates how to enable static website hosting for aws buckets. A demonstration of how the resources look in aws is also provided in this segment.
Erik demonstrates organizing and managing container repositories and creating a backend that supports the previously created frontend service.
Erik answers student questions regarding leveraging Pulumi for CI/CD pipelines, if lock state is available, and if documentation can be generated.
Managing CI/CD
Section Duration: 1 hour, 4 minutes
Erik walks through writing a technical design document regarding creating a CLI tool that contains service templates. A visual demonstration using a lucid chart is also covered in this segment.
Erik live codes a CLI tool that can read a build.json file, define service names, and service types to help automate the build process.
Erik demonstrates implementing a dockerfile containing ENV variables for service names and service types. Updating the build.json to allow for more overrides in the dockerfile is also covered in this segment.
Erik demonstrates implementing the ability for the CLI tool to read template files to generate the new dockerfile.
Erik briefly discusses configuring the CLI tool to operate remotely, hard coding the build path, and demonstrates writing the dockerfile. Running pre and post install commands are also covered in this segment.
Erik walks through writing and configuring a circleci.yml file to further automate building and testing.
Wrapping Up
Section Duration: 1 minute
Erik wraps up the course by providing a brief summary of DevOps and the goals of the course.
Learn Straight from the Experts Who Shape the Modern Web
- In-depth Courses
- Industry Leading Experts
- Learning Paths
- Live Interactive Workshops