10.4. SELECT
Table of Contents
Basic idea of `SELECT`
The SELECT statement reads data from a table and returns it as a result set.
Very simple form:
SELECT column1, column2
FROM table_name;Example, imagine a table:
users:
| id | username | age | |
|---|---|---|---|
| 1 | alice | alice@example.com | 25 |
| 2 | bob | bob@example.com | 31 |
| 3 | carol | carol@example.com | 29 |
Query:
SELECT id, username
FROM users;Result:
| id | username |
|---|---|
| 1 | alice |
| 2 | bob |
| 3 | carol |
Core rule:
SELECT defines what columns you want, FROM defines which table(s) you read from.
You can select all columns with *:
SELECT *
FROM users;
This returns every column in users. This is handy while learning, but in real applications you usually avoid SELECT * and specify only the columns you need.
Column lists and aliases
Selecting specific columns
You can list any number of columns:
SELECT username, email, age
FROM users;
Order matters: the result columns appear in the same order as in the SELECT list, not necessarily in the table definition order.
You can even repeat a column:
SELECT username, age, age
FROM users;
Result has three columns, the last two are both age.
This is rarely useful in real systems, but it shows that the SELECT list is independent from the table structure.
Column aliases with `AS`
Aliases rename columns in the result, not in the table. They are useful when:
- you compute values
- you have long or unclear column names
- you join tables (later chapter) and want clear names
Syntax:
SELECT column_name AS alias_name
FROM table_name;Examples:
SELECT
username AS user_name,
email AS contact_email
FROM users;Result:
| user_name | contact_email |
|---|---|
| alice | alice@example.com |
| bob | bob@example.com |
| carol | carol@example.com |
AS is optional, you can write:
SELECT
username user_name,
email contact_email
FROM users;
Both forms are equivalent. Using AS is usually clearer and easier to read.
Aliases can also be used for computed columns:
SELECT
username,
age + 1 AS age_next_year
FROM users;Result:
| username | age_next_year |
|---|---|
| alice | 26 |
| bob | 32 |
| carol | 30 |
Important: Aliases change only the column names in the query output, they do not change the actual column names in the database.
Selecting all columns with `*`
* means “all columns” from the tables in the FROM clause.
SELECT *
FROM users;
This returns all columns of users.
You can combine * with extra computed columns:
SELECT
*,
age + 10 AS age_in_10_years
FROM users;Result:
| id | username | age | age_in_10_years | |
|---|---|---|---|---|
| 1 | alice | alice@example.com | 25 | 35 |
| 2 | bob | bob@example.com | 31 | 41 |
| 3 | carol | carol@example.com | 29 | 39 |
Why `SELECT *` can be a problem in backends
For learning, SELECT * is fine. In real applications, it can be harmful:
- It may fetch more data than needed, which is slower.
- If someone adds a new big column (for example a large JSON field or image data) your app might suddenly start moving a lot more data.
- It can break code that depends on column order or count.
Better to explicitly list columns:
SELECT id, username, email, age
FROM users;Constants and simple expressions
You are not limited to table columns in the SELECT list. You can add:
- constants
- arithmetic expressions
- string operations
- functions (will be covered later but you will see a bit here)
Adding constant values
SELECT
username,
'ACTIVE' AS status
FROM users;Result:
| username | status |
|---|---|
| alice | ACTIVE |
| bob | ACTIVE |
| carol | ACTIVE |
Every row gets the same constant value in the status column.
You can also use numeric constants:
SELECT
username,
age,
18 AS legal_age_limit
FROM users;Result:
| username | age | legal_age_limit |
|---|---|---|
| alice | 25 | 18 |
| bob | 31 | 18 |
| carol | 29 | 18 |
Arithmetic expressions
Basic arithmetic works like in most programming languages:
| Operator | Meaning |
|---|---|
+ | addition |
- | subtraction |
* | multiplication |
/ | division |
Examples:
SELECT
username,
age,
age + 5 AS age_in_5_years,
age * 12 AS age_in_months,
age / 10.0 AS age_div_10
FROM users;Result:
| username | age | age_in_5_years | age_in_months | age_div_10 |
|---|---|---|---|---|
| alice | 25 | 30 | 300 | 2.5 |
| bob | 31 | 36 | 372 | 3.1 |
| carol | 29 | 34 | 348 | 2.9 |
You can mix column names and constants in expressions.
Tip: Always give expressions an alias. Otherwise the column name in the result is the expression text itself, which is hard to use and read.
Removing duplicate rows with `DISTINCT`
By default, SELECT returns one row for each matching row in the table, even if several rows have the same values in the selected columns.
DISTINCT removes duplicate rows from the result.
Syntax:
SELECT DISTINCT column1, column2, ...
FROM table_name;Imagine a simple table:
orders:
| id | user_id | status |
|---|---|---|
| 1 | 1 | pending |
| 2 | 2 | shipped |
| 3 | 1 | shipped |
| 4 | 3 | pending |
| 5 | 2 | shipped |
Without DISTINCT:
SELECT status
FROM orders;Result:
| status |
|---|
| pending |
| shipped |
| shipped |
| pending |
| shipped |
With DISTINCT:
SELECT DISTINCT status
FROM orders;Result:
| status |
|---|
| pending |
| shipped |
If you select more than one column, DISTINCT works on the combination of those columns.
Example:
SELECT DISTINCT user_id, status
FROM orders;Result:
| user_id | status |
|---|---|
| 1 | pending |
| 2 | shipped |
| 1 | shipped |
| 3 | pending |
Even though status = 'pending' appears multiple times, the pair (3, 'pending') is distinct from (1, 'pending').
Rule:
DISTINCT keeps only unique combinations of all selected columns together, not each column separately.
Basic filtering with `WHERE` (preview)
Full details of WHERE belong in the WHERE chapter, but it is very hard to talk about SELECT without touching it at all. You will see only simple examples here.
WHERE filters rows before they are returned. Only rows that satisfy the condition are included.
General pattern:
SELECT column_list
FROM table_name
WHERE condition;Examples:
-- Users older than 25
SELECT id, username, age
FROM users
WHERE age > 25;Result (with our sample data):
| id | username | age |
|---|---|---|
| 2 | bob | 31 |
| 3 | carol | 29 |
Another example:
-- Orders that are shipped
SELECT id, user_id, status
FROM orders
WHERE status = 'shipped';Result:
| id | user_id | status |
|---|---|---|
| 2 | 2 | shipped |
| 3 | 1 | shipped |
| 5 | 2 | shipped |
Later, in the WHERE chapter, you will learn about more complex conditions with AND, OR, IN, LIKE, and working with NULL.
Ordering results with `ORDER BY` (preview)
Again, full details belong in the ORDER BY chapter, but you need a quick idea here.
ORDER BY sorts the result rows.
General pattern:
SELECT column_list
FROM table_name
ORDER BY column1 [ASC|DESC], column2 [ASC|DESC], ...;ASCmeans ascending order, small to large, A to Z. It is the default.DESCmeans descending order, large to small, Z to A.
Example:
SELECT id, username, age
FROM users
ORDER BY age;Result:
| id | username | age |
|---|---|---|
| 1 | alice | 25 |
| 3 | carol | 29 |
| 2 | bob | 31 |
Now reverse the order:
SELECT id, username, age
FROM users
ORDER BY age DESC;Result:
| id | username | age |
|---|---|---|
| 2 | bob | 31 |
| 3 | carol | 29 |
| 1 | alice | 25 |
You can also sort by multiple columns:
SELECT id, username, age
FROM users
ORDER BY age DESC, username ASC;This sorts first by age descending, and for equal ages by username ascending.
Limiting the number of rows (`LIMIT` / `OFFSET`) (preview)
Limiting belongs more naturally with pagination, but it is very commonly used with simple SELECT queries.
In many database systems, you can restrict the number of rows using LIMIT.
General pattern:
SELECT column_list
FROM table_name
ORDER BY some_column
LIMIT n;
n is the maximum number of rows you want.
Example:
-- Only the first 2 users when ordered by id
SELECT id, username
FROM users
ORDER BY id
LIMIT 2;Result:
| id | username |
|---|---|
| 1 | alice |
| 2 | bob |
You can skip some rows using OFFSET:
SELECT id, username
FROM users
ORDER BY id
LIMIT 2 OFFSET 1;This means: skip the first row, then return 2 rows.
Result:
| id | username |
|---|---|
| 2 | bob |
| 3 | carol |
You will revisit these concepts in more depth when learning about pagination.
Practical examples for backend developers
To connect SELECT with typical backend tasks, imagine more realistic tables.
Example 1: Basic user listing for an admin API
Table users (extended):
| id | username | age | created_at | |
|---|---|---|---|---|
| 1 | alice | alice@example.com | 25 | 2024-01-01 10:00:00 |
| 2 | bob | bob@example.com | 31 | 2024-02-15 09:30:00 |
| 3 | carol | carol@example.com | 29 | 2024-03-05 11:45:00 |
Query for an admin list:
SELECT
id,
username,
email,
created_at
FROM users
ORDER BY created_at DESC
LIMIT 20;
This gives the 20 most recently created users for an admin endpoint like GET /admin/users.
Example 2: Status counts with constants
Imagine your backend needs to show the current status label together with each order.
orders:
| id | user_id | status | total_amount |
|---|---|---|---|
| 1 | 1 | pending | 49.99 |
| 2 | 2 | shipped | 19.99 |
| 3 | 1 | shipped | 5.00 |
You might want a label that you compute in the app, but during development you can test it in SQL:
SELECT
id,
status,
total_amount,
'USD' AS currency
FROM orders;Result:
| id | status | total_amount | currency |
|---|---|---|---|
| 1 | pending | 49.99 | USD |
| 2 | shipped | 19.99 | USD |
| 3 | shipped | 5.00 | USD |
Example 3: Selecting distinct values for filters
For building filter dropdowns in a UI, you can query unique values.
SELECT DISTINCT status
FROM orders
ORDER BY status;
Your backend endpoint could use this result to populate a filter list like ["pending", "shipped", "cancelled"].
Summary
SELECTdefines what data to return,FROMdefines from where.- You can:
- select specific columns:
SELECT id, username FROM users; - select all columns:
SELECT * FROM users; - give columns or expressions aliases with
ASfor clearer results. - include constants and arithmetic expressions in the
SELECTlist. - remove duplicate rows with
SELECT DISTINCT .... - preview basic filtering with
WHERE, sorting withORDER BY, and limiting rows withLIMIT/OFFSET.
In later chapters like WHERE, ORDER BY, GROUP BY, and JOINs, you will combine these building blocks into more powerful queries. For now, practice writing simple SELECT queries on a sample database, changing the column list, adding aliases, constants, and small expressions.
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!