24.2. Continuous Integration
Table of Contents
Why Continuous Integration Matters
Continuous Integration, often shortened to CI, is a practice where developers frequently merge their code changes into a shared repository and automatically verify that the changes do not break the project.
Instead of waiting days or weeks to integrate features, CI encourages you to integrate many small changes multiple times per day. Each integration triggers automated checks, such as running tests and linters.
In a backend context, CI becomes the safety net every time you push code to your API, database layer, background workers, or infrastructure scripts.
Key idea: CI is about frequent code integration combined with automatic checks that run on every change.
A simple timeline comparison helps:
| Approach | Integration Frequency | Manual Work | Risk of Breakage | Feedback Speed |
|---|---|---|---|---|
| No CI | Rare (big batches) | High | Very high | Slow |
| Basic CI (few tests) | Often (small batches) | Medium | Lower | Faster |
| Mature CI (full pipeline) | Very often | Low | Much lower | Very fast |
Backend projects become easier to maintain when you can trust an automated system to tell you quickly if something is broken.
Core Concepts of Continuous Integration
CI is not a single tool or service. It is a process built around several ideas that work together.
Shared main branch
A typical backend repository has one main integration branch, often called main or master. All new code, after being reviewed and tested, ends up here.
Developers create feature branches like:
feature/add-user-notificationsbugfix/fix-order-totalchore/update-dependencies
They push these branches, open pull requests (or merge requests), and use CI to verify that the branch is safe to merge.
Automated builds
A build step prepares your application for running:
- Installing dependencies
- Compiling or bundling where necessary
- Generating artifacts (for example a Docker image)
In a Python backend, the build step can be as simple as:
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txtThe CI system runs this automatically on every push or pull request so you do not have to do it manually.
Automated tests
Tests give you confidence that existing behavior still works. CI runs them every time you push.
Common test types for a backend:
| Test Type | Checks | Example |
|---|---|---|
| Unit tests | Individual functions or methods | Email validation function returns correct result |
| Integration | Components working together | API endpoint reads from PostgreSQL correctly |
| API tests | HTTP endpoints and responses | /api/orders returns 201 and correct JSON |
| Smoke tests | Very basic health checks | Service starts and health check endpoint works |
Running tests locally is good. Running them in CI is better, because every change is checked in a clean environment that resembles production.
Rule: Every push to a shared branch must trigger tests. If tests fail, do not merge.
Fast, frequent feedback
CI works only if feedback is fast.
- If a test suite takes 45 minutes to run, developers will stop caring about it.
- If it takes 3 minutes, developers are willing to wait and fix issues immediately.
For backend projects, aim for:
- A quick pipeline for every push that finishes in a few minutes.
- Heavier tests (for example full integration with many services) that may run less frequently, for example nightly.
Single source of truth
The CI pipeline is the trusted definition of how your project is built and verified.
This avoids the situation where:
- Developer A runs tests one way on their laptop.
- Developer B runs a different set of commands.
- Production is deployed in yet another way.
By encoding commands into CI config files (YAML or similar), you make the process explicit, repeatable, and reviewable.
Typical Continuous Integration Workflow
To understand CI, walk through a concrete developer story on a backend project.
Local work
- Pull the latest
mainbranch. - Create a new feature branch, for example
feature/add-task-search. - Implement new functionality.
- Run tests locally, at least for the parts you touched.
- Commit your changes.
Push and create a pull request
You push your branch:
git push origin feature/add-task-search
Then you open a pull request into main on GitHub, GitLab, or another platform.
At that moment, CI typically:
- Starts a new pipeline.
- Shows its status directly on the pull request, usually as a green check or a red cross.
CI pipeline stages
Most CI systems define stages that run in order.
A simple backend CI pipeline might have:
- Lint
- Run static analysis tools, for example
flake8,black --check,mypy. - Test
- Run unit tests and small integration tests, for example
pytest. - Build
- Build a Docker image or other deployment artifact.
Example of a simple logical flow:
| Stage | Example Commands | Purpose |
|---|---|---|
| lint | pip install -r dev-requirements.txt<br>flake8 . | Catch style or simple code issues |
| test | pytest -q | Ensure behavior is correct |
| build | docker build -t my-api:pr-123 . | Ensure code is buildable |
If any stage fails, the pipeline stops and marks the pull request as failing.
Fix and repeat
If CI fails:
- You inspect the logs in the CI interface.
- You fix the problem locally.
- You commit and push again.
- CI re-runs automatically on the new commit.
Once all stages pass and code review is complete, the branch merges into main.
Continuous Integration vs Continuous Delivery vs Continuous Deployment
These three concepts are related but not the same.
| Concept | Main Focus | Automation Level |
|---|---|---|
| Continuous Integration | Integrate and test code frequently | Build + tests on every change |
| Continuous Delivery | Keep code always deployable | CI + automatic packaging + manual deploy trigger |
| Continuous Deployment | Deploy automatically on every successful build | CI + CD + auto deploy to production |
In this chapter you focus only on Continuous Integration, that is build and test automation. Deployment automation is handled in separate chapters on Continuous Delivery, Continuous Deployment, and CI/CD pipelines.
What CI Does for Backend Projects
Backend applications often have more moving parts than small frontend apps. CI helps keep these parts consistent and working.
Consistent environments
Instead of each developer having a slightly different environment on their laptop, CI runs:
- On a known base image or virtual machine.
- With defined versions of Python, PostgreSQL, Redis, and other tools.
- With clear setup steps, for example installing dependencies and environment variables.
This reduces the classic line:
"It works on my machine."
If it does not work in CI, you treat that as the truth.
Catching integration bugs early
Even if your code works alone, integration with:
- Existing modules,
- The database schema,
- Authentication components,
- Background jobs,
can introduce subtle bugs.
By integrating small changes frequently, you discover integration problems while they are still easy to fix.
Enforcing quality standards
CI can run checks that are easy to forget:
- Code formatting (for example
black). - Static type checks (for example
mypy). - Security checks (for example dependency scanners).
- Linting (for example
flake8orpylint).
You do not have to remind team members to run these manually. The CI system enforces them consistently.
Simple Examples of CI Configuration
Concrete examples help make this less abstract. Imagine a basic Python/FastAPI backend.
Example: GitHub Actions CI for a Python backend
A minimal .github/workflows/ci.yml:
name: CI
on:
push:
branches: [ main ]
pull_request:
branches: [ main ]
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: Check out code
uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.11"
- name: Install dependencies
run: |
python -m venv .venv
source .venv/bin/activate
pip install -U pip
pip install -r requirements.txt
pip install -r dev-requirements.txt
- name: Run linters
run: |
source .venv/bin/activate
flake8 .
black --check .
mypy .
- name: Run tests
env:
DATABASE_URL: "postgresql://test:test@localhost:5432/testdb"
run: |
source .venv/bin/activate
pytest -qKey observations:
- The job runs on
pushandpull_requesttomain. - It checks out the code.
- It sets up Python.
- It installs dependencies.
- It runs linting and tests.
You do not need to memorize GitHub Actions syntax in this chapter. Instead, notice how the CI file becomes the script that defines your integration process.
Example: GitLab CI for a backend project
A simple .gitlab-ci.yml:
stages:
- lint
- test
variables:
PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"
lint:
stage: lint
image: python:3.11
script:
- pip install -r dev-requirements.txt
- flake8 .
- black --check .
- mypy .
artifacts:
when: always
paths:
- flake8.log
expire_in: 1 week
test:
stage: test
image: python:3.11
services:
- name: postgres:15
alias: db
variables:
POSTGRES_DB: testdb
POSTGRES_USER: test
POSTGRES_PASSWORD: test
DATABASE_URL: "postgresql://test:test@db:5432/testdb"
script:
- pip install -r requirements.txt
- pip install -r dev-requirements.txt
- pytest -qHere:
lintandtestare stages.- Tests run against a real PostgreSQL service that CI spins up.
Again, the idea is: define how to integrate and test your backend using configuration, not manual steps.
Good Practices for Continuous Integration
Even a simple CI setup benefits from some basic principles.
Keep pipelines fast
A quick pipeline encourages frequent integration.
Ideas to keep it fast:
- Run unit tests on every push.
- Run heavier tests, for example very slow integration or load tests, on a schedule such as nightly.
- Cache dependencies when the CI system supports it.
For example, caching pip packages:
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements*.txt') }}
restore-keys: |
${{ runner.os }}-pip-Fail fast
Configure CI to fail as soon as a serious problem is detected.
For example:
- If dependencies cannot be installed, stop.
- If tests fail, stop.
- If linting fails, you do not need to run tests for that commit.
This saves compute time and gives feedback faster.
Treat warnings seriously
If tests pass but CI shows warnings, do not ignore them.
Warnings can indicate:
- Deprecated functions that will break later.
- Security issues in dependencies.
- Flaky tests that sometimes fail and sometimes pass.
Fixing them early keeps your backend more stable.
Run CI on every branch that might be merged
Running CI only on main is too late. A branch could break the build and block everyone.
Configure CI to run on:
- Pull requests into main.
- Possibly feature branches when pushed.
This makes sure you never merge unverified code.
Rule: Do not merge a pull request if the CI status is failing or missing.
Simple CI Checklist for Beginners
When you start a new backend project, you can use this short list.
| Step | Question to Ask |
|---|---|
| Define main branch | What is the integration branch (for example main)? |
| Choose a CI platform | GitHub Actions, GitLab CI, or others? |
| Trigger conditions | Should CI run on push, pull request, or both? |
| Install dependencies | How will Python and packages be installed? |
| Run tests | What pytest command should CI run? |
| Run quality checks | Which linters and formatters will you use? |
| Pipeline speed | Does it finish in a few minutes? |
If you can answer these questions, you have the basics of Continuous Integration in place for your backend project.
Views: 0
Where to Move
Move chapter:
- ☰ 1. Introduction to Backend Development
- ☰ 1.1. What Is Backend Development?
- ☰ 1.2. Frontend vs Backend
- ☰ 1.3. How Web Applications Work
- ☰ 1.4. Client-Server Architecture
- ☰ 1.5. Request-Response Cycle
- ☰ 1.6. Static vs Dynamic Websites
- ☰ 1.7. Backend Developer Responsibilities
- ☰ 1.8. Backend Development Roadmap
-
- ☰ 2. How the Web Works
- ☰ 2.1. The Internet and the Web
- ☰ 2.2. IP Addresses
- ☰ 2.3. Domain Names
- ☰ 2.4. DNS
- ☰ 2.5. Ports
- ☰ 2.6. TCP/IP Basics
- ☰ 2.7. HTTP and HTTPS
- ☰ 2.8. HTTP Requests
- ☰ 2.9. HTTP Responses
- ☰ 2.10. HTTP Methods
- ☰ 2.11. HTTP Status Codes
- ☰ 2.12. HTTP Headers
- ☰ 2.13. Cookies
- ☰ 2.14. Sessions
- ☰ 2.15. What Happens When You Enter a URL?
-
- ☰ 3. Development Environment
- ☰ 3.1. Choosing an Operating System
- ☰ 3.2. Linux Basics for Backend Developers
- ☰ 3.3. Command Line Basics
- ☰ 3.4. Environment Variables
- ☰ 3.5. Installing Development Tools
- ☰ 3.6. Code Editors and IDEs
- ☰ 3.7. Git
- ☰ 3.8. GitHub and GitLab
- ☰ 3.9. Creating Your First Repository
- ☰ 3.10. Branches and Commits
- ☰ 3.11. Basic Git Workflow
-
- ☰ 4. Programming Fundamentals
- ☰ 4.1. Variables and Data Types
- ☰ 4.2. Operators
- ☰ 4.3. Conditions
- ☰ 4.4. Loops
- ☰ 4.5. Functions
- ☰ 4.6. Data Structures
- ☰ 4.7. Error Handling
- ☰ 4.8. Modules and Packages
- ☰ 4.9. File Handling
- ☰ 4.10. Object-Oriented Programming
- ☰ 4.11. Classes and Objects
- ☰ 4.12. Inheritance and Composition
- ☰ 4.13. Clean Code Principles
-
- ☰ 5. Python for Backend Development
- ☰ 5.1. Introduction to Python
- ☰ 5.2. Installing Python
- ☰ 5.3. Virtual Environments
- ☰ 5.4. pip and Package Management
- ☰ 5.5. Python Project Structure
- ☰ 5.6. Functions and Type Hints
- ☰ 5.7. Classes and Dataclasses
- ☰ 5.8. Exceptions
- ☰ 5.9. Working with Files
- ☰ 5.9.1. File Downloads
- ☰ 5.9.2. File Validation
- ☰ 5.9.3. Image Uploads
- ☰ 5.9.4. Local File Storage
- ☰ 5.9.5. Object Storage
- ☰ 5.9.6. S3-Compatible Storage
- ☰ 5.9.7. Presigned URLs
- ☰ 5.9.8. Secure File Handling
-
- ☰ 5.10. JSON
- ☰ 5.11. Date and Time
- ☰ 5.12. Logging
- ☰ 5.13. Configuration
- ☰ 5.14. Environment Variables
- ☰ 5.15. Async Programming
- ☰ 5.16. Python Backend Best Practices
-
- ☰ 6. Introduction to Web Backends
- ☰ 6.1. Building a Simple Web Server
- ☰ 6.2. Routing
- ☰ 6.3. URL Parameters
- ☰ 6.4. Query Parameters
- ☰ 6.5. Request Bodies
- ☰ 6.6. Form Data
- ☰ 6.7. JSON Requests
- ☰ 6.8. Returning Responses
- ☰ 6.9. Templates
- ☰ 6.10. Static Files
- ☰ 6.11. Middleware
- ☰ 6.12. Application Configuration
-
- ☰ 7. REST APIs
- ☰ 7.1. What Is an API?
- ☰ 7.2. What Is REST?
- ☰ 7.3. Resources and Endpoints
- ☰ 7.4. RESTful URL Design
- ☰ 7.5. HTTP Methods in REST
- ☰ 7.6. GET Requests
- ☰ 7.7. POST Requests
- ☰ 7.8. PUT Requests
- ☰ 7.9. PATCH Requests
- ☰ 7.10. DELETE Requests
- ☰ 7.11. Request Validation
- ☰ 7.12. Response Models
- ☰ 7.13. HTTP Status Codes
- ☰ 7.14. Error Responses
- ☰ 7.15. Pagination
- ☰ 7.16. Filtering
- ☰ 7.17. Sorting
- ☰ 7.18. Searching
- ☰ 7.19. API Versioning
- ☰ 7.20. API Documentation
- ☰ 7.21. OpenAPI and Swagger
-
- ☰ 8. FastAPI
- ☰ 8.1. Introduction to FastAPI
- ☰ 8.2. Routes and Path Operations
- ☰ 8.3. Path Parameters
- ☰ 8.4. Pydantic Models
- ☰ 8.5. Data Validation
- ☰ 8.6. Dependency Injection
- ☰ 8.7. Exception Handling
- ☰ 8.8. Background Tasks
- ☰ 8.9. File Uploads
- ☰ 8.10. Async Endpoints
- ☰ 8.11. FastAPI Project Structure
- ☰ 8.12. Building a Complete REST API
-
- ☰ 9. Databases
- ☰ 9.1. Introduction to Databases
- ☰ 9.2. Relational vs NoSQL Databases
- ☰ 9.3. Tables, Rows, and Columns
- ☰ 9.4. Primary Keys
- ☰ 9.5. Foreign Keys
- ☰ 9.6. Relationships
- ☰ 9.7. One-to-One Relationships
- ☰ 9.8. One-to-Many Relationships
- ☰ 9.9. Many-to-Many Relationships
- ☰ 9.10. Database Schema Design
- ☰ 9.11. Normalization
- ☰ 9.12. Indexes
- ☰ 9.13. Transactions
- ☰ 9.14. ACID Properties
-
- ☰ 10. SQL
- ☰ 10.1. Introduction to SQL
- ☰ 10.2. CREATE
- ☰ 10.3. INSERT
- ☰ 10.4. SELECT
- ☰ 10.5. UPDATE
- ☰ 10.6. DELETE
- ☰ 10.7. WHERE
- ☰ 10.8. ORDER BY
- ☰ 10.9. GROUP BY
- ☰ 10.10. Aggregate Functions
- ☰ 10.11. JOINs
- ☰ 10.12. Subqueries
- ☰ 10.13. Constraints
- ☰ 10.14. Indexes
- ☰ 10.15. Transactions
- ☰ 10.16. Common Table Expressions
- ☰ 10.17. SQL Performance Basics
-
- ☰ 11. PostgreSQL
- ☰ 11.1. Introduction to PostgreSQL
- ☰ 11.2. Installing PostgreSQL
- ☰ 11.3. Creating Databases
- ☰ 11.4. Users and Roles
- ☰ 11.5. Permissions
- ☰ 11.6. PostgreSQL Data Types
- ☰ 11.7. Constraints
- ☰ 11.8. Indexes
- ☰ 11.9. Transactions
- ☰ 11.10. JSON Data
- ☰ 11.11. Backup and Restore
- ☰ 11.12. PostgreSQL Performance Basics
-
- ☰ 12. ORM and Database Integration
- ☰ 12.1. What Is an ORM?
- ☰ 12.2. SQLAlchemy
- ☰ 12.3. Models
- ☰ 12.4. Database Sessions
- ☰ 12.5. Creating Records
- ☰ 12.6. Reading Records
- ☰ 12.7. Updating Records
- ☰ 12.8. Deleting Records
- ☰ 12.9. Relationships
- ☰ 12.10. Queries
- ☰ 12.11. Transactions
- ☰ 12.12. Connection Pooling
- ☰ 12.13. Database Migrations
- ☰ 12.14. Alembic
- ☰ 12.15. Repository Pattern
-
- ☰ 13. Authentication
- ☰ 13.1. Authentication vs Authorization
- ☰ 13.2. Password Storage
- ☰ 13.3. Password Hashing
- ☰ 13.4. Registration
- ☰ 13.5. Login
- ☰ 13.6. Tokens
- ☰ 13.7. JSON Web Tokens
- ☰ 13.8. Access Tokens
- ☰ 13.9. Refresh Tokens
- ☰ 13.10. OAuth 2.0
- ☰ 13.11. OpenID Connect
- ☰ 13.12. Social Login
- ☰ 13.13. Logout
- ☰ 13.14. Password Reset
- ☰ 13.15. Email Verification
- ☰ 13.16. Multi-Factor Authentication
-
- ☰ 14. Authorization
- ☰ 14.1. Users and Permissions
- ☰ 14.2. Role-Based Access Control
- ☰ 14.3. Permission-Based Access Control
- ☰ 14.4. Protecting API Endpoints
- ☰ 14.5. Admin Permissions
- ☰ 14.6. Resource Ownership
- ☰ 14.7. Authorization Best Practices
-
- ☰ 15. Backend Security
- ☰ 15.1. Introduction to Web Security
- ☰ 15.2. HTTPS and TLS
- ☰ 15.3. SQL Injection
- ☰ 15.4. Cross-Site Scripting
- ☰ 15.5. Cross-Site Request Forgery
- ☰ 15.6. CORS
- ☰ 15.7. Authentication Attacks
- ☰ 15.8. Brute-Force Protection
- ☰ 15.9. Rate Limiting
- ☰ 15.10. Input Validation
- ☰ 15.11. Secure Password Storage
- ☰ 15.12. Secrets Management
- ☰ 15.13. Secure Cookies
- ☰ 15.14. Security Headers
- ☰ 15.15. File Upload Security
- ☰ 15.16. Dependency Vulnerabilities
- ☰ 15.17. OWASP Top 10
-
- ☰ 16. Caching
- ☰ 16.1. Why Caching Matters
- ☰ 16.2. Application Caching
- ☰ 16.3. Redis
- ☰ 16.3.1. Introduction to Redis
- ☰ 16.3.2. Installing Redis
- ☰ 16.3.3. Keys and Values
- ☰ 16.3.4. Expiration
- ☰ 16.3.5. Distributed Locks
-
- ☰ 16.4. Cache Keys
- ☰ 16.5. Cache Invalidation
- ☰ 16.6. Caching Database Queries
- ☰ 16.7. Distributed Caching
-
- ☰ 17. Background Processing
- ☰ 17.1. Synchronous vs Asynchronous Tasks
- ☰ 17.2. Background Jobs
- ☰ 17.3. Message Queues
- ☰ 17.4. Celery
- ☰ 17.5. Redis as a Message Broker
- ☰ 17.6. Scheduled Tasks
- ☰ 17.7. Retry Strategies
- ☰ 17.8. Handling Failed Jobs
- ☰ 17.9. Email Jobs
- ☰ 17.10. Long-Running Tasks
-
- ☰ 18. Email
- ☰ 18.1. How Email Works
- ☰ 18.2. SMTP
- ☰ 18.3. Sending Emails
- ☰ 18.4. HTML Emails
- ☰ 18.5. Transactional Emails
- ☰ 18.6. Password Reset Emails
- ☰ 18.7. Background Email Delivery
- ☰ 18.8. Email Delivery Best Practices
-
- ☰ 19. Testing
- ☰ 19.1. Why Backend Testing Matters
- ☰ 19.2. Unit Testing
- ☰ 19.3. Integration Testing
- ☰ 19.4. API Testing
- ☰ 19.5. pytest
- ☰ 19.6. Fixtures
- ☰ 19.7. Mocking
- ☰ 19.8. Testing Databases
- ☰ 19.9. Testing Authentication
- ☰ 19.10. Testing FastAPI
- ☰ 19.11. Test Coverage
- ☰ 19.12. Automated Testing
-
- ☰ 20. Logging and Monitoring
- ☰ 20.1. Application Logging
- ☰ 20.2. Log Levels
- ☰ 20.3. Structured Logging
- ☰ 20.4. Request Logging
- ☰ 20.5. Error Logging
- ☰ 20.6. Metrics
- ☰ 20.7. Health Checks
- ☰ 20.8. Monitoring
- ☰ 20.9. Prometheus
- ☰ 20.10. Grafana
- ☰ 20.11. Alerting
- ☰ 20.12. Error Tracking
- ☰ 20.13. Observability Basics
-
- ☰ 21. Docker
- ☰ 21.1. Introduction to Containers
- ☰ 21.2. Docker Architecture
- ☰ 21.3. Images
- ☰ 21.4. Containers
- ☰ 21.5. Dockerfiles
- ☰ 21.6. Building Images
- ☰ 21.7. Running Containers
- ☰ 21.8. Volumes
- ☰ 21.9. Networks
- ☰ 21.10. Docker Compose
- ☰ 21.11. FastAPI with Docker
- ☰ 21.12. PostgreSQL with Docker
- ☰ 21.13. Redis with Docker
- ☰ 21.14. Multi-Container Applications
- ☰ 21.15. Production Docker Best Practices
-
- ☰ 22. Web Servers and Reverse Proxies
- ☰ 22.1. Application Servers
- ☰ 22.2. Uvicorn
- ☰ 22.3. Gunicorn
- ☰ 22.4. Reverse Proxies
- ☰ 22.5. Nginx
- ☰ 22.6. Traefik
- ☰ 22.7. HTTPS
- ☰ 22.8. TLS Certificates
- ☰ 22.9. Let's Encrypt
- ☰ 22.10. Load Balancing
-
- ☰ 23. Deployment
- ☰ 23.1. Development vs Production
- ☰ 23.2. Preparing an Application for Production
- ☰ 23.3. Linux Server Setup
- ☰ 23.4. Deploying with Docker
- ☰ 23.5. Environment Configuration
- ☰ 23.6. Managing Secrets
- ☰ 23.7. HTTPS Configuration
- ☰ 23.8. Production Logging
- ☰ 23.9. Backups
- ☰ 23.10. Zero-Downtime Deployment
- ☰ 23.11. Rollbacks
-
- ☰ 24. CI/CD
- ☰ 24.1. Introduction to CI/CD
- ☰ 24.2. Continuous Integration
- ☰ 24.3. Continuous Delivery
- ☰ 24.4. Continuous Deployment
- ☰ 24.5. CI/CD Pipelines
- ☰ 24.6. GitHub Actions
- ☰ 24.7. GitLab CI/CD
- ☰ 24.8. Building Docker Images
- ☰ 24.9. Container Registries
- ☰ 24.10. Deployment Pipelines
- ☰ 24.11. Staging Environments
- ☰ 24.12. Production Environments
- ☰ 24.13. Rollback Strategies
-
- ☰ 25. Backend Architecture
- ☰ 25.1. Monolithic Architecture
- ☰ 25.2. Modular Monoliths
- ☰ 25.3. Microservices
- ☰ 25.4. Layered Architecture
- ☰ 25.5. Service Layer
- ☰ 25.6. Separation of Concerns
- ☰ 25.7. Domain-Driven Design Basics
- ☰ 25.8. Event-Driven Architecture
- ☰ 25.9. Choosing an Architecture
-
- ☰ 26. Performance and Scalability
- ☰ 26.1. Understanding Backend Performance
- ☰ 26.2. CPU-Bound vs I/O-Bound Work
- ☰ 26.3. Asynchronous Programming
- ☰ 26.4. Database Optimization
- ☰ 26.5. Query Optimization
- ☰ 26.6. Indexing
- ☰ 26.7. Load Balancing
- ☰ 26.8. Horizontal Scaling
- ☰ 26.9. Vertical Scaling
- ☰ 26.10. Stateless Applications
- ☰ 26.11. Performance Testing
- ☰ 26.12. Load Testing
-
- ☰ 27. Advanced API Development
- ☰ 27.1. WebSockets
- ☰ 27.2. Server-Sent Events
- ☰ 27.3. GraphQL
- ☰ 27.4. Webhooks
- ☰ 27.5. Idempotency
- ☰ 27.6. API Rate Limiting
- ☰ 27.7. API Keys
- ☰ 27.8. API Gateways
- ☰ 27.9. Distributed APIs
- ☰ 27.10. Real-Time Applications
-
- ☰ 28. Production Backend Engineering
- ☰ 28.1. Configuration Management
- ☰ 28.2. Database Backups
- ☰ 28.3. Disaster Recovery
- ☰ 28.4. Graceful Shutdown
- ☰ 28.5. Fault Tolerance
- ☰ 28.6. Circuit Breakers
- ☰ 28.7. High Availability
- ☰ 28.8. Monitoring Production Systems
- ☰ 28.9. Incident Response
-
- ☰ 29. Project 1: Task Management API
- ☰ 29.1. Project Requirements
- ☰ 29.2. Project Structure
- ☰ 29.3. Database Design
- ☰ 29.4. CRUD Operations
- ☰ 29.5. Validation
-
- ☰ 30. Project 2: Authentication System
- ☰ 30.1. User Registration
- ☰ 30.2. JWT Authentication
- ☰ 30.3. Role-Based Authorization
- ☰ 30.4. Security Testing
-
- ☰ 31. Project 3: E-Commerce Backend
- ☰ 31.1. Architecture
- ☰ 31.2. User Management
- ☰ 31.3. Product Management
- ☰ 31.4. Categories
- ☰ 31.5. Shopping Cart
- ☰ 31.6. Orders
- ☰ 31.7. Inventory
- ☰ 31.8. Payments
- ☰ 31.9. Admin API
-
- ☰ 32. Final Project: Production Backend
- ☰ 32.1. Planning the Application
- ☰ 32.2. Designing the Architecture
- ☰ 32.3. Designing the Database
- ☰ 32.4. Building the REST API
- ☰ 32.5. Authentication and Authorization
- ☰ 32.6. PostgreSQL Integration
- ☰ 32.7. Redis Integration
- ☰ 32.8. Background Workers
- ☰ 32.9. File Storage
- ☰ 32.10. Dockerizing the Application
- ☰ 32.11. CI/CD Pipeline
- ☰ 32.12. Production Deployment
- ☰ 32.13. HTTPS and Domain Setup
- ☰ 32.14. Performance Optimization
- ☰ 32.15. Security Review
- ☰ 32.16. Documentation
-
- ☰ 33. Backend Developer Roadmap
- ☰ 33.1. What You Should Know Now
- ☰ 33.2. Building a Portfolio
- ☰ 33.3. Creating Backend Projects
- ☰ 33.4. Contributing to Open Source
- ☰ 33.5. Preparing for Backend Interviews
- ☰ 33.6. Backend Interview Questions
- ☰ 33.7. Database Interview Questions
- ☰ 33.8. API Interview Questions
- ☰ 33.9. Linux and Docker Interview Questions
- ☰ 33.10. Where to Go Next
-
Comments
Please login to add a comment.
Don't have an account? Register now!