CI/CD for Serverless Applications

# CHAPTER 14

CI/CD for Serverless Applications #

1. Introduction #

2. Learning Objectives #

• Define the principles of Continuous Integration (CI) and Continuous Deployment (CD).

• Understand the role of Git and GitHub in modern workflows.

• Introduce the Serverless Framework (CLI tool).

• Construct a YAML-based deployment pipeline.

• Implement automated testing before deployment.

3. Beginner-Friendly Explanation #

• Manual Deployment (The Old Way): The author writes the book, prints it on their home printer, drives to the bookstore, and physically puts the book on the shelf. If they made a typo, they have to drive back and do it all again.

• CI/CD (The Automated Way): The author types the book on their computer and presses "Save" (Git Push). A robot (GitHub Actions) instantly picks up the manuscript, scans it for spelling errors (Automated Tests), formats it perfectly, drives it to the bookstore, and places it on the shelf (Automated Deployment). The author never leaves their desk, and broken books never make it to the shelf.

4. The Serverless Framework #

*Example serverless.yml:*

service: my-cool-api
provider:
  name: aws
  runtime: nodejs20.x

functions:
  helloUser:
    handler: handler.hello
    events:
      - http:
          path: /hello
          method: get

By simply typing serverless deploy in your terminal, the tool automatically creates the API Gateway, provisions the Lambda function, uploads the code, and links them together!

5. Continuous Integration (CI) #

1. 1. It downloads the code into a fresh, isolated container.

1. 2. It runs npm install.

1. 3. It runs npm test (Unit tests to ensure the code actually works).

1. 4. If a test fails, the pipeline halts immediately, placing a big red "X" on the GitHub Pull Request. The broken code is blocked from merging.

6. Continuous Deployment (CD) #

1. 1. It securely authenticates to AWS using hidden API keys.

1. 2. It runs the serverless deploy command.

1. 3. The new code is pushed directly to the live production environment within seconds.

7. Mini Project: Create a GitHub Actions CI/CD Workflow #

Step-by-Step Overview:

1. 1. In your project repository on GitHub, navigate to Settings > Secrets. Add your AWSACCESSKEYID and AWSSECRETACCESSKEY.

1. 2. In your code repository, create a file at .github/workflows/deploy.yml.

1. 3. Define the workflow:

name: Deploy Serverless API

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v3

      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: '20'

      - name: Install Dependencies
        run: npm install

      - name: Run Tests
        run: npm test

      - name: Deploy to AWS
        uses: serverless/github-action@v3
        with:
          args: deploy
        env:
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

1. 4. The Result: Every time you type git push origin main on your laptop, GitHub spins up a server, installs Node, runs your tests, and seamlessly deploys your API to AWS. You achieve total automation.

8. Real-World Scenarios #

9. Best Practices #

• Separate Environments: Never deploy directly to Production. Use the Serverless Framework's "Stage" feature. When a developer pushes to the dev branch, the pipeline deploys to the --stage dev environment. When code is merged to main, the pipeline deploys to --stage prod. This keeps testing data completely separate from real customer data.

10. Cost Optimization Tips #

• GitHub Actions Free Tier: GitHub Actions provides 2,000 free build minutes every month for private repositories. For personal projects and small startups, your entire enterprise-grade CI/CD pipeline will cost $0.

11. Exercises #

1. 1. Explain the danger of manual deployments and how CI/CD mitigates this risk.

1. 2. What is the specific purpose of the "Unit Testing" step within the Continuous Integration (CI) phase?

12. FAQs #

13. Interview Questions #

• Q: Describe the architectural flow of a CI/CD pipeline utilizing GitHub Actions and the Serverless Framework, from a developer's git commit to a live production update.

• Q: Contrast the operational risk of managing AWS Lambda functions via the AWS Console UI versus defining them declaratively in a serverless.yml configuration file.

14. Summary #

15. Next Chapter Recommendation #