7.6. GET Requests
Table of Contents
Understanding GET Requests
In REST APIs, GET is the most common HTTP method. It is used to retrieve data from the server without changing anything on the server.
This chapter focuses only on GET in the context of REST, not on other HTTP methods or full REST design, which are covered in separate chapters.
Key idea:
GET requests retrieve data and must not change server state.
They should be safe and idempotent.
What a GET Request Is For
A GET request asks the server:
"Give me the representation of this resource."
Examples of what you might fetch with GET:
- A single user by ID
- A list of products
- The details of a single product
- A list of orders for a user
- A search result for
?q=shoes
In REST, typical GET endpoints might look like:
GET /usersGET /users/42GET /productsGET /products/123GET /orders?status=pending
In all these examples, you are reading information.
Typical RESTful GET Patterns
| Endpoint | Meaning |
|---|---|
GET /resources | List or search resources |
GET /resources/{id} | Get one resource by ID |
GET /users/me | Get information about the current authenticated user |
GET /stats | Read-only statistics or summary information |
Where GET Data Goes: URL, Path, Query
A GET request does not usually send a request body in REST APIs. Data is typically sent in:
- The path
- Example:
/users/42 42is a path parameter.- The query string
- Example:
/users?country=US&status=active&page=2 country,status,pageare query parameters.
Example: Path vs Query in GET
GET /users/42- Path parameter:
42represents the resource ID GET /users?country=US&status=active&page=2- Query parameters:
country = USstatus = activepage = 2
Typical usage:
- Path parameters: identify a single specific resource
- Query parameters: filter, search, sort, and paginate lists
You will see path parameters and query parameters in much more detail in dedicated chapters, but for GET requests the key idea is:
Rule:
Use the path to point at what you want, and use the query string to refine how you want it.
GET Request Examples
Simple GET Request
Request:
GET /users/42 HTTP/1.1
Host: api.example.com
Accept: application/jsonTypical response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"id": 42,
"name": "Alice",
"email": "alice@example.com"
}GET With Query Parameters
Request:
GET /products?category=books&sort=price_asc&page=1&limit=10 HTTP/1.1
Host: api.example.com
Accept: application/jsonTypical response:
HTTP/1.1 200 OK
Content-Type: application/json
{
"items": [
{
"id": 101,
"title": "Learn Backend Development",
"price": 29.99
},
{
"id": 102,
"title": "Advanced REST APIs",
"price": 34.99
}
],
"page": 1,
"limit": 10,
"total": 57
}Here the query parameters control filtering, sorting, and pagination, which are covered more deeply in later chapters.
GET and RESTful URLs
In the chapter on RESTful URL design you will see general rules, but here are examples focused only on GET:
| Operation | Recommended GET URL |
|---|---|
| List all users | GET /users |
| Get one user | GET /users/{user_id} |
| Get all posts for a user | GET /users/{user_id}/posts |
| Get one post of a user | GET /users/{user_id}/posts/{post_id} |
| Search users by name and country | GET /users?name=alice&country=US |
| Get paginated list of products | GET /products?page=2&limit=50 |
| Get filtered, sorted products | GET /products?category=shoes&sort=-price |
Notice that all of these are reads. No creation, updates, or deletions are done with GET.
Safety and Idempotency of GET
Two important properties of GET:
Safe
A method is safe if it does not change server state.
GET should be used only for reading. For example:
- Reading products: safe
- Getting user profile: safe
- Triggering a payment: not safe for GET
If a GET request changes your database, that is usually a design problem.
Idempotent
A method is idempotent if making the same request many times has the same effect as making it once.
For GET:
- First GET
/users/42retrieves user 42 - The second, third, and 100th GET
/users/42do the same thing - There is no additional change caused by repeating the request
Design rule:
GET must be safe and idempotent. Do not use GET to create, modify, or delete data.
GET Request Body: Should You Use It?
The HTTP standard allows a body in a GET request, but in practice:
- Many servers and frameworks ignore the body on GET
- Caches and proxies may ignore it
- Developer tools often do not handle it well
In REST APIs for backend development, it is a strong convention to not use a body for GET.
Use:
- Path and query parameters for filters, options, and identifiers
- POST, if you truly need a complex body and cannot express it as query parameters
GET and Caching
GET works very well with caching, which is one reason it must be safe.
Because GET does not modify data, intermediate systems such as:
- Browsers
- Reverse proxies
- CDNs
can cache responses and reuse them.
You will learn HTTP caching in detail in a separate chapter, but for GET:
- A
GET /productsresponse can be cached for a short time - If another client asks for the same URL, the cache can return the stored response instead of hitting your backend again
Example:
GET /products/123 HTTP/1.1
Host: api.example.com
Accept: application/jsonResponse:
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: max-age=60
{
"id": 123,
"name": "Wireless Mouse",
"price": 19.99
}
The header Cache-Control: max-age=60 tells caches they can reuse this response for 60 seconds.
Practical hint:
If your endpoint changes data, do not use GET. If something uses GET, design it so it can be safely cached.
Common GET Status Codes
When you handle GET requests in a REST API, you usually return:
| Status code | Meaning | When to use for GET |
|---|---|---|
200 OK | Success with a response body | Resource found and returned |
204 No Content | Success with no body | Request succeeded but nothing to return |
301/302 | Redirect | Resource moved or redirect to another URL |
400 Bad Request | Client error, invalid input | Query parameters invalid |
401 Unauthorized | Not authenticated | Authentication required |
403 Forbidden | Not allowed | Authenticated but not allowed |
404 Not Found | Resource does not exist | No resource with that ID or URL |
500 Internal Server Error | Server error | Something went wrong on the server |
You will study status codes more deeply in the dedicated chapter, but for GET it is helpful to recognize:
200when data is returned404when the resource is missing400when the query is invalid
Example:
GET /users/999999 HTTP/1.1
Host: api.example.com
Accept: application/jsonHTTP/1.1 404 Not Found
Content-Type: application/json
{
"detail": "User not found"
}GET in a Simple REST API: Practical Examples
To make GET concrete, here are example designs for a small REST API.
1. Users API
| Operation | Method | URL | Request body | Response body |
|---|---|---|---|---|
| List users | GET | /users | None | List of users |
| Get user by ID | GET | /users/{id} | None | Single user |
| Search users by name | GET | /users?name=… | None | Filtered list |
Example requests:
GET /users HTTP/1.1
Host: api.example.com
Accept: application/jsonGET /users/42 HTTP/1.1
Host: api.example.com
Accept: application/jsonGET /users?name=alice&page=2 HTTP/1.1
Host: api.example.com
Accept: application/json2. Products API
| Operation | Method | URL |
|---|---|---|
| List products | GET | /products |
| Filter products by category | GET | /products?category=electronics |
| Filter and sort | GET | /products?category=electronics&sort=price_desc |
| Get single product | GET | /products/{product_id} |
| Get reviews for a product | GET | /products/{product_id}/reviews |
Example GET for a list:
GET /products?category=electronics&sort=price_desc&page=1&limit=20 HTTP/1.1
Host: api.example.com
Accept: application/jsonExample GET for a single resource:
GET /products/987 HTTP/1.1
Host: api.example.com
Accept: application/jsonCommon Mistakes to Avoid with GET
1. Using GET to Modify Data
Bad design:
GET /create-user?name=aliceGET /delete-post?id=123
These change data but use GET.
Better:
POST /userswith a JSON body to create a userDELETE /posts/123to delete a post
2. Putting Sensitive Data in the URL
Avoid sending sensitive information in query parameters, for example:
GET /login?email=alice@example.com&password=secretProblems:
- URLs can be logged by servers and proxies
- Browser history stores them
- They can appear in analytics logs
Sensitive data such as passwords, tokens, or personal information should not be sent in GET query strings.
3. Overly Complex Query Parameters
Sometimes people try to encode very complex filters in a single query string parameter, for example:
GET /search?filter=(status='active' AND age>18) OR city='London'This becomes hard to parse and maintain. In many simple cases you can split it:
GET /users?status=active&min_age=18&city=LondonFor very complex queries you might prefer:
- A POST endpoint with a JSON body, or
- A dedicated search service, or
- Simpler filter rules
How GET Is Used by Browsers and Tools
Browsers
When you:
- Type a URL in the address bar
- Click a regular link
- Refresh a page
the browser sends a GET request.
Example:
You enter https://example.com/products?category=books
The browser sends:
GET /products?category=books HTTP/1.1
Host: example.comHTML and GET
An HTML form without a method uses GET by default:
<form action="/search">
<input name="q" placeholder="Search">
<button type="submit">Search</button>
</form>If you type "backend" and submit, the browser sends:
GET /search?q=backend HTTP/1.1
Host: example.comThis is why search engines often use URLs like:
https://www.google.com/search?q=backend+development
Designing Good GET Endpoints in REST APIs
When you design GET endpoints for a REST API, keep these practical guidelines in mind:
- Use nouns, not verbs, in URLs
- Good:
GET /users/42 - Bad:
GET /getUser?id=42 - Use plural resource names for collections
GET /usersGET /products- Support filtering and pagination with query parameters
GET /products?category=books&page=2&limit=20- Return appropriate status codes
200 OKwhen data is found404 Not Foundwhen the resource does not exist400 Bad Requestwhen parameters are invalid- Do not require a body
- All needed input should be in the path or query string
- Keep them read-only
- Never create, update, or delete data with GET
Summary
- GET is used to retrieve representations of resources.
- It should be safe and idempotent, and must not change server state.
- Data for GET requests should be passed via the path and query string, not in the body.
- GET works very well with caching.
- Use GET with clear, noun-based RESTful URLs, for example:
GET /usersGET /users/{id}GET /products?category=books&page=1
In later chapters you will learn in more detail how GET interacts with pagination, filtering, sorting, and how to implement GET endpoints in a specific framework such as FastAPI.
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!