11.2. Installing PostgreSQL
Table of Contents
Why Installation Matters
Before you can use PostgreSQL from your backend code, you need a running PostgreSQL server and the basic tools to connect to it. In this chapter you will:
- Install PostgreSQL on the 3 main platforms: Linux, macOS, and Windows
- Verify that the server is running
- Connect using the command line tool
psql - Create a test database and user
You do not need to be a system administration expert. You only need enough to get a local development database running.
Goal: By the end of this chapter you should be able to run psql, connect to a local PostgreSQL instance, and create a simple test database.
Installing PostgreSQL on Linux
On Linux, PostgreSQL is usually installed through your distribution package manager. The commands differ slightly between distributions, but the ideas are the same.
Ubuntu and Debian
On Ubuntu and Debian you can install PostgreSQL from the official PostgreSQL repository, which often has more recent versions than the default system repository.
Step 1: Add PostgreSQL repository
Open a terminal and run:
sudo apt update
sudo apt install curl ca-certificates gnupgAdd the PostgreSQL signing key and repository:
# Import the repository key
curl -fsSL https://www.postgresql.org/media/keys/ACCC4CF8.asc \
| sudo gpg --dearmor -o /usr/share/keyrings/postgresql.gpg
# Add the repository (for Ubuntu 22.04 as an example)
echo "deb [signed-by=/usr/share/keyrings/postgresql.gpg] \
http://apt.postgresql.org/pub/repos/apt jammy-pgdg main" \
| sudo tee /etc/apt/sources.list.d/pgdg.list
Change jammy to focal, bullseye, etc, depending on your distribution. You can find the correct codename on the PostgreSQL downloads page.
Step 2: Install PostgreSQL
Update and install:
sudo apt update
sudo apt install postgresql postgresql-contribpostgresqlis the serverpostgresql-contribincludes useful extra extensions
Step 3: Check service status
PostgreSQL should start automatically. Check:
sudo systemctl status postgresqlYou should see something like:
Active: active (exited) or active (running)If it is not running, start it:
sudo systemctl start postgresqlAnd enable on boot:
sudo systemctl enable postgresqlStep 4: Switch to the `postgres` system user
On Linux, PostgreSQL creates a special operating system user named postgres that owns the server process.
sudo -i -u postgresYour shell prompt should change to something like:
postgres@your-machine:~$
From here you can run psql without a password:
psql
To exit psql type:
\q
Then exit the postgres user:
exitCommon package commands (Ubuntu/Debian)
| Task | Command |
|---|---|
| Start PostgreSQL | sudo systemctl start postgresql |
| Stop PostgreSQL | sudo systemctl stop postgresql |
| Restart PostgreSQL | sudo systemctl restart postgresql |
| Status | sudo systemctl status postgresql |
| Version (server) | psql --version or postgres -V |
Fedora, CentOS, and RHEL
On Fedora and related distributions you usually use dnf or yum.
For a typical Fedora installation:
sudo dnf install postgresql-server postgresql-contribFor CentOS / RHEL, you might also need to initialize the database:
sudo /usr/bin/postgresql-setup --initdbThen start and enable the service:
sudo systemctl start postgresql
sudo systemctl enable postgresqlCheck status:
sudo systemctl status postgresql
Usage (switch user and run psql) is similar to Ubuntu:
sudo -i -u postgres
psqlInstalling PostgreSQL on macOS
On macOS you have several options. For development, two popular ones are:
- Homebrew
- PostgreSQL.app
Option 1: Homebrew
Homebrew is a package manager for macOS. It is a good choice if you like working in the terminal.
Step 1: Install Homebrew (if needed)
If you do not have Homebrew yet, run in Terminal:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Follow the instructions and then ensure brew is in your PATH as explained by the installer.
Step 2: Install PostgreSQL
brew update
brew install postgresqlHomebrew may print extra instructions at the end, read them carefully. They often include helpful tips about managing the service.
Step 3: Start the PostgreSQL service
brew services start postgresqlCheck that it is running:
brew services list
You should see postgresql with status started.
Step 4: Test `psql`
PostgreSQL client tools are now available in your shell.
psql --versionTo connect to the default database with your macOS username:
psql postgresIf everything works, you will see a prompt similar to:
postgres=#
Type \q to exit.
Option 2: PostgreSQL.app
PostgreSQL.app is a standalone app that includes PostgreSQL and common tools, convenient if you want a more graphical and self-contained installation.
- Go to https://postgresapp.com
- Download the latest version for your macOS
- Drag and drop PostgreSQL.app into your Applications folder
- Open PostgreSQL.app. It will initialize and start a PostgreSQL server
To use psql from the terminal, PostgreSQL.app offers a menu item:
- Open PostgreSQL.app
- Click the gear icon
- Choose “Open psql” or “Copy psql command”
- Or add its bin directory to your
PATHas described in the documentation
Installing PostgreSQL on Windows
On Windows, the easiest way is the official installer provided by EnterpriseDB.
Step 1: Download the installer
- Go to https://www.postgresql.org/download/windows/
- Click the link to installers provided by EnterpriseDB
- Download the latest stable version (for example, 16.x) for Windows
You will get an .exe installer file.
Step 2: Run the installer
Double click the installer and follow the wizard:
- Installation directory: choose a location, or accept the default, for example
C:\Program Files\PostgreSQL\16\ - Components: select at least:
- PostgreSQL Server
- pgAdmin 4 (graphical admin tool)
- Command Line Tools
- Data directory: accept the default or pick a location
- Password: set a strong password for the PostgreSQL superuser
postgres. Write it down, you will need it later - Port: default is
5432. Normally you should keep this - Locale: choose your locale or accept default
Finish the installation. The installer will start the PostgreSQL service.
Step 3: Verify service status
On Windows, PostgreSQL runs as a Windows service.
- Press
Win + R - Type
services.mscand press Enter - Look for a service named like:
postgresql-x64-16or similar - The status should be “Running”
If it is not running, right click the service and choose “Start”.
Step 4: Test connectivity with `psql`
You can use either:
- Windows Command Prompt
- PowerShell
- The “SQL Shell (psql)” shortcut that the installer usually adds
Example using “SQL Shell (psql)”:
- Open the Start menu
- Search for “SQL Shell (psql)” and open it
- It will ask:
Server [localhost]:
Database [postgres]:
Port [5432]:
Username [postgres]:Press Enter for Server, Database, Port, then type:
Username: postgresThen type the password you set in the installer.
If login is successful, you will see the postgres=# prompt.
Type:
SELECT version();Then:
\qto exit.
Verifying Your Installation
After installation on any platform, you should check two things:
- The server is running
- You can connect with
psql
Check the server status
Linux
sudo systemctl status postgresql
You want active (running) or similar.
macOS with Homebrew
brew services list
Look for postgresql started.
Windows
Use services.msc and check that the PostgreSQL service is running.
Check `psql` version
Run this in your terminal or command prompt:
psql --versionYou should see output similar to:
psql (PostgreSQL) 16.0
If your system says command not found or similar, then psql is not in your PATH or not installed. For:
- Linux: ensure
postgresql-clientis installed, or thepostgresqlpackage itself - macOS Homebrew: ensure the Homebrew bin directory is in your
PATH - PostgreSQL.app: add its bin directory to your
PATHas described in the app - Windows: ensure you installed Command Line Tools and restarted your terminal
Basic `psql` Usage
Once PostgreSQL is installed, psql is the main command line tool you will use to:
- Run SQL queries
- Create databases and users
- Inspect schemas, tables, and more
You do not need to memorize everything now. Just learn the basic commands you will use daily.
Connecting to PostgreSQL
The connection syntax is:
psql -h HOST -p PORT -U USERNAME -d DATABASEIf you omit some options, it will use defaults:
- Host:
localhost - Port:
5432 - Username: your operating system username (sometimes)
- Database: same as username, or
postgres
Examples
Linux (as postgres OS user):
sudo -i -u postgres
psqlmacOS with your system user:
psql postgresWindows:
psql -U postgres -d postgres -h localhost -p 5432
When prompted for a password, type it and press Enter. psql shows nothing as you type, this is normal.
Useful `psql` meta commands
psql commands start with a backslash. They are not SQL, they are client commands.
| Command | Description |
|---|---|
\q | Exit psql |
\l | List databases |
\c db | Connect to database db |
\dt | List tables in current database |
\du | List roles (users) |
\d table_name | Describe table structure |
\? | Help for meta commands |
Example:
\l
\c postgres
\dt
\duCreating a Test Database and User
You now have PostgreSQL running. For backend development, you typically do not use the default superuser from your application. Instead, you create:
- A database for your project
- A user (role) with a password
- Permissions for that user on the database
Rule: Never use the postgres superuser from your application. Always create a separate, limited user for each application.
Step 1: Connect as an admin
On Linux, run:
sudo -i -u postgres
psql
On macOS / Windows, connect as postgres (superuser) using psql:
psql -U postgres -d postgres -h localhostEnter the password if prompted.
You should see the postgres=# prompt.
Step 2: Create a database
Create a new database named myapp_dev:
CREATE DATABASE myapp_dev;Check that it exists:
\l
You should see myapp_dev in the list.
Step 3: Create a user with password
Create a login role that your backend application will use.
Example user myapp_user with password myapp_password:
CREATE USER myapp_user WITH PASSWORD 'myapp_password';For development, this is fine. For production, you should use a stronger password and secure storage, which you will cover in later chapters.
Step 4: Grant privileges on the database
Give the new user permission to work with the new database.
First, connect to the database:
\c myapp_devYou will see:
You are now connected to database "myapp_dev"Then grant privileges:
GRANT ALL PRIVILEGES ON DATABASE myapp_dev TO myapp_user;At this point:
myapp_devis a new databasemyapp_usercan connect to it and create tables
Step 5: Test login as the new user
Exit psql:
\q
Connect again using myapp_user:
psql -U myapp_user -d myapp_dev -h localhost
Enter the password myapp_password.
Now create a simple table to confirm permissions:
CREATE TABLE test_table (
id SERIAL PRIMARY KEY,
name TEXT NOT NULL
);
INSERT INTO test_table (name) VALUES ('hello'), ('postgres');
SELECT * FROM test_table;You should see:
id | name
----+---------
1 | hello
2 | postgres
(2 rows)
Then type \q to exit.
Typical Connection Details for Backend Apps
Your backend application will usually need the following fields to connect to PostgreSQL:
| Field | Typical development value |
|---|---|
| Host | localhost |
| Port | 5432 |
| Database | myapp_dev |
| User | myapp_user |
| Password | myapp_password |
In many backend frameworks, you will configure a database URL like:
postgresql://myapp_user:myapp_password@localhost:5432/myapp_devLater chapters will show how to use this with ORMs and FastAPI.
Common Installation Problems and Fixes
You might run into some typical problems. Here are simple checks.
Port already in use
If another PostgreSQL instance or service uses port 5432, you might see errors like:
could not bind IPv4 socket: Address already in useSolutions:
- Stop the other PostgreSQL service
- Change the port in
postgresql.confand restart - On Linux, inspect which process uses the port:
sudo lsof -i :5432Cannot connect: “connection refused”
Check that the service is running:
- Linux:
sudo systemctl status postgresql - macOS Homebrew:
brew services list - Windows:
services.msc
If it is stopped, start it.
Authentication failed
Errors like:
psql: FATAL: password authentication failed for user "myapp_user"Possible issues:
- Wrong password
- User does not exist
- Using the wrong host or port
You can reset the password as superuser:
ALTER USER myapp_user WITH PASSWORD 'new_password';Then try again.
Summary
You now know how to:
- Install PostgreSQL on Linux, macOS, and Windows
- Start and stop the PostgreSQL service
- Use
psqlto connect to the server - Create a dedicated database and user for your application
- Confirm everything works with a simple test table
This setup is enough for development work. In later chapters you will learn how to design schemas, use SQL, and connect PostgreSQL to your backend code using ORMs and connection URLs.
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!