16.3.2. Installing Redis
Table of Contents
Getting Ready to Install Redis
This chapter walks you through installing Redis on different platforms and verifying that it works. You do not need previous Redis knowledge, but you should be comfortable running simple commands in a terminal.
We will cover:
- Installing Redis on Linux, macOS, and Windows
- Running Redis as a background service
- Basic configuration and testing your installation
Throughout, we will keep things simple so you can get Redis running quickly on your development machine.
Rule: Always install Redis from a trusted source (official package manager, official website, or well known container registry). Never download random binaries from unknown websites.
Installing Redis on Linux
Linux is the most common environment for running Redis in production. For development, you can usually use your distribution package manager.
Installing on Ubuntu / Debian
Use apt from the terminal.
- Update package lists:
sudo apt update- Install Redis:
sudo apt install redis-server- Check that Redis is installed:
redis-server --versionYou should see something like:
Redis server v=7.0.15 sha=... bits=64 ...Starting and Stopping Redis (systemd)
On modern Ubuntu and Debian, Redis runs as a systemd service.
- Start Redis:
sudo systemctl start redis-server- Stop Redis:
sudo systemctl stop redis-server- Restart Redis:
sudo systemctl restart redis-server- Check status:
sudo systemctl status redis-server
Look for the line Active: active (running) which means Redis is running.
Enable Redis on Boot
To start Redis automatically when the system boots:
sudo systemctl enable redis-serverIf you later want to disable auto start:
sudo systemctl disable redis-serverInstalling on CentOS / Rocky Linux / RHEL
Many RHEL based systems do not ship a recent Redis in their default repositories. A common approach is to use the Remi repository, which provides newer versions.
- Install EPEL and Remi repositories (example for CentOS 8 or similar):
sudo dnf install epel-release
sudo dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm- Enable the Redis module from Remi:
sudo dnf module enable redis:remi-7.0 -y- Install Redis:
sudo dnf install redis -y- Start and enable Redis:
sudo systemctl start redis
sudo systemctl enable redis- Check version:
redis-server --versionBuilding Redis from Source (Any Linux)
If your package manager provides an old version, you can compile Redis yourself.
- Install build tools (Ubuntu example):
sudo apt update
sudo apt install build-essential tcl- Download the latest stable Redis from the official website:
curl -O https://download.redis.io/redis-stable.tar.gz
tar xzf redis-stable.tar.gz
cd redis-stable- Compile:
make- Optionally run tests (this can take a while):
make test- Install binaries:
sudo make install
This usually installs redis-server and redis-cli into /usr/local/bin.
- Start Redis quickly for development:
redis-server
This starts Redis in the foreground. Press Ctrl + C to stop.
You can also provide a configuration file:
redis-server /path/to/redis.confInstalling Redis on macOS
On macOS, the easiest way is to use Homebrew. If you do not have Homebrew, first install it from https://brew.sh by following their instructions.
Installing with Homebrew
- Update Homebrew:
brew update- Install Redis:
brew install redis- Check the version:
redis-server --versionYou should see Redis version information printed.
Running Redis on macOS
There are two main ways to run Redis with Homebrew.
1. Run Redis Manually (Foreground)
Start the server:
redis-server
You will see logs in your terminal. Press Ctrl + C to stop it.
This is good for quick experiments.
2. Run Redis as a Background Service
To run Redis in the background:
brew services start redisTo stop the service:
brew services stop redisTo restart:
brew services restart redisTo see running services:
brew services listLook for a line like:
redis started your-username ...which means Redis is running.
Installing Redis on Windows
Redis does not officially support Windows natively anymore. For learning and development, you have three common options:
- Use the Windows Subsystem for Linux (WSL)
- Use Docker
- Use the memurai project or older community ports (not recommended for long term learning)
For this course, WSL or Docker is recommended, because both are very close to Linux environments.
Option 1: Redis on Windows with WSL
WSL lets you run a Linux distribution inside Windows.
Step 1: Install WSL and a Linux Distribution
In PowerShell (as Administrator):
wsl --installBy default, this installs Ubuntu. After reboot, follow the prompts to set up a username and password in Ubuntu.
Step 2: Install Redis inside WSL
Open the Ubuntu terminal from the Start menu and run:
sudo apt update
sudo apt install redis-serverStart Redis:
sudo service redis-server startCheck status:
sudo service redis-server status
You can now use redis-cli inside WSL:
redis-cli pingExpected response:
PONGOption 2: Redis on Windows with Docker
If you use Docker Desktop on Windows, you can run a Linux Redis container.
- Install Docker Desktop from https://www.docker.com/products/docker-desktop and make sure it is running.
- Pull the official Redis image:
docker pull redis:latest- Start a Redis container:
docker run -d --name redis-dev -p 6379:6379 redis:latestExplanation:
-druns in detached mode--name redis-devnames the container-p 6379:6379exposes port 6379 to your Windows host
- Check running containers:
docker ps- To stop the container:
docker stop redis-dev- To start it again:
docker start redis-dev
You can now connect to Redis from Windows using a Redis client on localhost:6379.
Basic Redis Configuration
Full configuration is covered later in the Redis chapter. For now, you only need minimal adjustments to get started safely in development.
Finding the Redis Configuration File
Common locations:
| OS / Install method | Typical path |
|---|---|
| Ubuntu / Debian package | /etc/redis/redis.conf |
| RHEL / CentOS package | /etc/redis.conf |
| macOS Homebrew | /usr/local/etc/redis.conf or similar |
| Source build | redis.conf in the source directory |
You can always search for it, for example:
sudo find / -name "redis.conf" 2>/dev/nullStarting Redis with a Specific Config
If you want to use a custom configuration file, you can copy the default redis.conf and then run:
redis-server /path/to/your-redis.confFor example:
cp /etc/redis/redis.conf ~/dev-redis.conf
redis-server ~/dev-redis.confThis is useful when you want different settings for development and production.
Making Basic Development Friendly Changes
In development, two very common config tweaks are:
- Bind to local interface only
- Disable or relax authentication (only on a trusted local machine)
Open your config file with a text editor, for example on Ubuntu:
sudo nano /etc/redis/redis.confBind Address
Look for a line like:
bind 127.0.0.1 ::1This restricts Redis to accept connections only from the local machine. This is good during development.
If you see a line like:
# bind 127.0.0.1 ::1
uncomment it by removing the # to avoid listening on all interfaces.
Protected Mode
You may see:
protected-mode yes
Keep this as yes for safety in development.
Require Password
Config line:
# requirepass yourpasswordFor simple local development, you can keep this commented, so no password is required. If you enable it:
requirepass verysecretpassword
Then you must authenticate in redis-cli:
AUTH verysecretpasswordRule: Never run Redis without a password on a server that is accessible from the internet. For production systems, always use authentication and proper firewall rules.
After changing the config, restart Redis:
On Ubuntu / Debian:
sudo systemctl restart redis-serverOn macOS (Homebrew):
brew services restart redisOn Docker:
docker restart redis-devTesting Your Redis Installation
After installation, you should verify that Redis is running and accepting commands.
Using redis-cli
redis-cli is the standard command line client that comes with Redis.
Simple Connection Test
In a terminal:
redis-cli ping
If Redis is running on localhost:6379 with no password, you should see:
PONGIf you set a password:
redis-cli
AUTH verysecretpassword
PINGExpected:
OK
PONGBasic Commands
Try some simple operations.
- Set and get a key:
redis-cli SET greeting "Hello, Redis!"
redis-cli GET greetingOutput:
"Hello, Redis!"- Check key existence:
redis-cli EXISTS greeting
If the key exists, Redis returns 1. If not, it returns 0.
- Delete a key:
redis-cli DEL greeting
redis-cli EXISTS greeting
You should see 0 after delete.
- Use the interactive shell:
redis-cliThen inside the prompt:
127.0.0.1:6379> SET counter 1
OK
127.0.0.1:6379> INCR counter
(integer) 2
127.0.0.1:6379> GET counter
"2"
127.0.0.1:6379> EXITConnecting From an Application (High Level View)
Later in the course you will connect to Redis from languages like Python. A minimal Python example, just to test connectivity, looks like this:
import redis
client = redis.Redis(host="localhost", port=6379, db=0)
client.set("language", "Python")
value = client.get("language")
print(value) # b'Python'
If this script runs without errors and prints b'Python' then Redis is working and your client library can connect.
You do not need to memorize this code now. It is only to show what a successful connection looks like from a program.
Common Installation Problems and Quick Fixes
Here are some frequent issues you may hit and how to resolve them.
Problem: `redis-server: command not found`
Possible causes and actions:
| Cause | Fix |
|---|---|
| Package not installed | Install via apt, dnf, brew, or Docker as described above |
Binary not in PATH | Use full path, for example /usr/local/bin/redis-server |
| Wrong shell session (e.g. outside WSL) | Make sure you run commands inside the correct environment or shell |
To locate Redis:
which redis-serveror
command -v redis-serverIf those commands return nothing, Redis is not installed in your current environment.
Problem: `Could not connect to Redis at 127.0.0.1:6379`
This usually means the server is not running, or is listening on a different host or port.
Checklist:
- Check if Redis is running:
- On systemd based systems:
systemctl status redis-server- With Homebrew:
brew services list- With Docker:
docker ps- If it is not running, start or restart it.
- Check the port in
redis.conf. Look for:
port 6379If you changed the port, call:
redis-cli -p NEW_PORT pingProblem: Authentication Error
If you see:
NOAUTH Authentication required.
It means requirepass is configured. Run:
redis-cli
AUTH yourpassword
PINGIf you forgot the password in a local development setup:
- Stop Redis
- Edit
redis.confand comment outrequirepass - Start Redis again
Do not do this on a shared or remote server.
Summary
In this chapter you learned how to:
- Install Redis on Linux, macOS, and Windows (using WSL or Docker)
- Start, stop, and restart the Redis server
- Locate and use the basic Redis configuration file
- Test your installation with
redis-cliusing commands likePING,SET,GET, andDEL - Recognize and fix some common installation problems
With Redis installed and running successfully, you are ready to explore keys, values, and the powerful data structures that Redis provides in the next chapters.
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!