3.5. Installing Development Tools
Table of Contents
Why Development Tools Matter
Before you write any backend code, you need a set of tools installed on your machine. These tools help you:
- Write code comfortably
- Run and test your applications
- Manage dependencies and versions
- Collaborate with others
In this chapter you will learn what to install and how to install it, with examples on Windows, macOS, and Linux. Later chapters will explain how to use each tool in depth, so here you focus on getting a solid, working setup.
Core Categories of Development Tools
For backend development, you usually need at least:
| Category | Examples | Purpose |
|---|---|---|
| Programming language | Python | Execute your backend logic |
| Package manager | pip | Install third party libraries |
| Version control | Git | Track changes, collaborate |
| Editor / IDE | VS Code, PyCharm | Write and navigate code |
| Terminal / Shell | PowerShell, Command Prompt, Bash, zsh | Run commands and tools |
| Database tools | psql (PostgreSQL), pgAdmin, DBeaver | Work with databases |
| Container tools | Docker Desktop, Docker Engine | Run apps in containers (later stages) |
You do not need all advanced tools on day one, but having the basics ready prevents frustration later.
General Installation Principles
Use Official Sources
Always download tools from their official websites or your operating system’s package manager.
Important rule
Only install development tools from trusted, official sources, such as:
- The official project website
- Your OS package manager (apt, dnf, pacman, Homebrew, etc)
- Trusted app stores (Microsoft Store, Apple App Store)
This reduces the risk of malware and inconsistent builds.
Examples of official sources:
- Python: https://www.python.org
- Git: https://git-scm.com
- VS Code: https://code.visualstudio.com
On Linux, using your distribution’s package manager is usually the best approach.
Prefer Command Line Installation When Possible
If you feel comfortable with the terminal, use it to install tools. It is:
- Easier to document and repeat
- Easier to automate later
- Clearer for troubleshooting
Example on Ubuntu:
sudo apt update
sudo apt install git python3 python3-pipExample on macOS with Homebrew:
brew install git pythonIf you are a complete beginner, it is fine to start with graphical installers and gradually move to command line.
Installing Tools on Windows
1. Installing a Terminal Environment
You will use the terminal a lot as a backend developer.
Windows Terminal
- Open Microsoft Store.
- Search for Windows Terminal.
- Click Get or Install.
Windows Terminal lets you open multiple shells, such as:
- PowerShell
- Command Prompt
- WSL (if installed)
Optional: Windows Subsystem for Linux (WSL)
WSL gives you a Linux environment inside Windows, which is very close to typical server environments.
To install WSL (Windows 10/11):
- Open PowerShell as Administrator.
- Run:
wsl --install- Restart your computer if asked.
- Choose a Linux distribution, for example Ubuntu, and set a username and password.
Later, you will be able to open Ubuntu inside Windows Terminal and use Linux commands.
2. Installing Python on Windows
- Go to https://www.python.org/downloads/windows/
- Download the latest stable Python 3.x installer (64-bit).
- Run the installer.
- On the first screen, check:
- Add Python 3.x to PATH (very important)
- Click Install Now and follow the prompts.
Verify Python installation
Open PowerShell or Command Prompt and run:
python --versionYou should see something like:
Python 3.12.1
If python does not work, try:
py --version
If that works, you can run Python scripts using py instead of python.
pip on Windows
pip is usually installed together with Python. Check with:
pip --versionIf this does not work, try:
py -m pip --version
Later, you will use pip to install backend libraries such as FastAPI and SQLAlchemy.
3. Installing Git on Windows
- Go to https://git-scm.com/download/win
- Download the installer.
- Run it and keep the defaults unless you know what you are doing.
- When asked about the default editor, you can choose Use Visual Studio Code as Git’s default editor if you will use VS Code.
- When asked about PATH, select Git from the command line and also from 3rd-party software.
Verify Git installation
Open PowerShell and run:
git --versionExpected output:
git version 2.45.0.windows.14. Installing a Code Editor on Windows
Visual Studio Code (recommended)
- Go to https://code.visualstudio.com/
- Download User Installer for Windows.
- Run the installer.
- Optionally check:
- Add "Open with Code" action to Windows Explorer file context menu
- Add "Open with Code" action to Windows Explorer directory context menu
- Finish installation.
Install useful VS Code extensions
Open VS Code, go to the Extensions panel, and search for:
- Python (by Microsoft)
- Pylance (if not included)
- GitLens (for Git enhancements)
- Docker (later when you start using Docker)
These will help autocompletion, linting, and Git integration.
5. Optional: Installing Database Tools on Windows
PostgreSQL
For backend work you often use PostgreSQL.
- Go to https://www.postgresql.org/download/windows/
- Click Download the installer.
- Choose the latest version and run the installer.
- Note the password you set for the
postgresuser. - Optionally install pgAdmin (checked by default), which is a graphical tool for working with PostgreSQL.
Verify with:
psql --version
If psql is not found, you may need to:
- Add PostgreSQL’s
bindirectory to your PATH, or - Use the full path, for example:
& "C:\Program Files\PostgreSQL\16\bin\psql.exe" --version
Installing Tools on macOS
1. Installing a Terminal Environment
macOS includes the Terminal app by default.
- Open Launchpad
- Search for Terminal
- Open it
Many backend developers on macOS install iTerm2 for a better experience, but the built-in Terminal is fine.
2. Installing Homebrew (recommended)
Homebrew is a package manager for macOS and makes installing tools simple.
Open Terminal and run:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"Follow the instructions. At the end, it will show commands to add Homebrew to your PATH. Run those commands.
Verify with:
brew --version3. Installing Python on macOS
macOS might come with a system Python. You should install your own Python 3 version.
With Homebrew:
brew install pythonVerify:
python3 --versionYou should see something like:
Python 3.12.1
You will usually use python3 instead of python on macOS.
pip is installed together with Python, use:
pip3 --version4. Installing Git on macOS
Git may already be available through Xcode Command Line Tools. Check:
git --versionIf it asks to install command line tools, accept. Or install Git via Homebrew:
brew install gitVerify again:
git --version5. Installing a Code Editor on macOS
Visual Studio Code
- Go to https://code.visualstudio.com/
- Download the macOS version.
- Open the downloaded
.zipand drag Visual Studio Code.app to the Applications folder.
Add the code command (optional but useful):
- Open VS Code.
- Open the Command Palette (View → Command Palette, or
Cmd + Shift + P). - Search for Shell Command: Install 'code' command in PATH and run it.
You can now open a folder from the terminal:
code my-projectInstall the same extensions as described in the Windows section (Python, GitLens, Docker, etc).
6. Optional: Installing PostgreSQL on macOS
With Homebrew:
brew install postgresqlStart the service:
brew services start postgresqlVerify:
psql --versionYou can also use graphical tools like pgAdmin or DBeaver if you prefer a GUI.
Installing Tools on Linux
Linux distributions differ slightly, but the basic approach is the same. Here are examples for Ubuntu or Debian based systems.
1. Updating Package Lists
Always update your package list first:
sudo apt update
On other distributions, you might use dnf, yum, or pacman instead.
2. Installing Python on Linux
Most distributions have Python 3 installed. Check with:
python3 --versionIf missing or outdated, install:
sudo apt install python3 python3-pipVerify:
python3 --version
pip3 --version
Later, you might use tools like pyenv to manage multiple Python versions, but for now the system Python is usually enough.
3. Installing Git on Linux
On Debian / Ubuntu:
sudo apt install gitVerify:
git --versionOn Fedora:
sudo dnf install gitOn Arch:
sudo pacman -S git4. Installing a Code Editor on Linux
Visual Studio Code
Using Microsoft’s repository on Ubuntu:
sudo apt update
sudo apt install wget gpg
wget -qO- https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/code stable main" | sudo tee /etc/apt/sources.list.d/vscode.list > /dev/null
sudo apt update
sudo apt install code
After that, you can run code from the terminal.
Or download the .deb or .rpm package directly from the VS Code website and install it with your package manager.
Install the same extensions as before (Python, GitLens, Docker, etc).
5. Optional: Installing PostgreSQL on Linux
On Ubuntu / Debian:
sudo apt install postgresql postgresql-contribCheck status:
sudo systemctl status postgresqlVerify version:
psql --versionOn other distributions, use their package manager with the appropriate package names.
Checking and Managing PATH
Many installation problems come from tools not being in your PATH. The PATH is an environment variable that tells your system where to look for executable programs.
You can see your PATH:
- Windows (PowerShell):
echo $Env:PATH- macOS / Linux:
echo $PATH
If a command like python or git is installed but not found, your PATH may not include the directory where it was installed.
Important rule
If a tool is installed but the command is "not found", check:
- Is it actually installed?
- Where is the executable located?
- Is that directory included in your PATH?
You must not blindly download the same tool multiple times before checking PATH. That often creates more confusion.
Examples:
- On Windows, if Python is installed but
pythonis not found, you may need to reinstall with Add Python to PATH checked. - On Linux, you might need to add a directory like
$HOME/.local/binto your PATH in.bashrcor.zshrc.
Verifying Your Setup With a Simple Project
After installing tools, create a tiny test to confirm everything works.
1. Create a project folder
Windows (PowerShell):
mkdir backend-test
cd backend-testmacOS / Linux:
mkdir backend-test
cd backend-test2. Initialize Git
git initYou should see:
Initialized empty Git repository in ...3. Create a simple Python file
Create a file hello.py with this content:
def main():
print("Hello, backend world!")
if __name__ == "__main__":
main()4. Run the Python file
- Windows (if
pythonworks):
python hello.py
or if you use py:
py hello.py- macOS / Linux:
python3 hello.pyYou should see:
Hello, backend world!5. Commit the file with Git
git add hello.py
git commit -m "Add hello backend script"If this works without errors, then:
- Python is installed and works
- Git is installed and works
- Your editor can open the folder and files
You now have a basic but functional development environment.
Common Installation Problems and How to Approach Them
Here are some typical issues beginners hit and how to think about solving them.
| Problem | Likely Cause | First Steps |
|---|---|---|
python not recognized | Not installed or not in PATH | Check installation, try py or python3 |
pip not found | Different name or PATH issue | Try py -m pip, python3 -m pip |
| Git not recognized | Git not installed or PATH issue | Run git --version, reinstall from official source |
VS Code code command not found | PATH setup missing | Use built-in "Install 'code' command in PATH" feature |
| Permission denied errors on Linux/macOS | Missing sudo or incorrect permissions | Read the error carefully, add sudo only when needed |
| PostgreSQL commands not found | PostgreSQL’s bin directory not in PATH | Find install path, add to PATH, or use full path |
Whenever you encounter issues, do the following:
- Read the entire error message, do not just glance at the first line.
- Copy the error message into a search engine, including your OS and tool name.
- Prefer answers from official documentation or high quality sources.
What You Should Have Ready After This Chapter
By the end of this chapter you should have:
- A working terminal or shell environment on your OS
- Python 3 installed and accessible from the command line
pipavailable for managing Python packages- Git installed and working
- A code editor such as VS Code with Python support enabled
- (Optional, but recommended) PostgreSQL installed with
psqlavailable
You do not need everything perfectly tuned. The goal is to be able to:
- Open a folder in your editor
- Run a Python script from the terminal
- Track files with Git
In later chapters, you will refine this environment with virtual environments, better configurations, and additional tools.
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!