18.4. HTML Emails
Table of Contents
Why HTML Emails Matter
Plain text emails are simple and reliable, but many real applications need richer messages. Think of:
- Password reset emails with a big “Reset password” button
- Order confirmations with tables of items
- Welcome emails with your logo and brand colors
All of these are HTML emails. They are small web pages, but with very strict rules.
In this chapter you will not learn how to send emails. You will focus on how to build HTML email content that works in real inboxes.
Key idea: HTML emails are like tiny web pages, but email clients support old and limited HTML and CSS. You must code them in a careful, old‑school way.
HTML vs Plain Text Emails
Plain Text Emails
A plain text email contains only characters, no formatting:
Hi Alice,
Your order has been shipped!
Track it here:
https://example.com/track/123
Thanks,
Example StorePros:
- Very compatible with all clients and devices
- Small and fast
- Easy to generate from backend code
Cons:
- No colors, no bold, no images, no layout
- Easy to miss links or important information
HTML Emails
HTML emails support formatting and structure:
<html>
<body>
<p>Hi Alice,</p>
<p><strong>Your order has been shipped!</strong></p>
<p>
Track it here:
<a href="https://example.com/track/123">View tracking status</a>
</p>
<p>Thanks,<br>Example Store</p>
</body>
</html>Pros:
- Better branding: logo, fonts, colors
- Clear CTAs (call to action) with buttons
- Tables for invoices and order summaries
Cons:
- Rendering is inconsistent across email clients
- More likely to break if you use modern CSS
- Requires more testing
In practice, many applications send multipart emails with both versions:
- A
text/plainpart - A
text/htmlpart
The email client chooses which one to show.
Rule: Always provide a plain text fallback when sending HTML emails. This improves deliverability and accessibility.
Core Structure of an HTML Email
Basic HTML Skeleton
Email HTML usually looks like this:
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Your subject here</title>
</head>
<body>
<!-- Content -->
</body>
</html>
Some clients ignore <head> contents, but including it is still good practice.
Use Tables for Layout
Modern web pages often use flexbox or CSS grid. Email clients, especially Outlook, often do not support them well. For layout you usually use <table> tags.
Example: a simple one‑column email layout:
<body style="margin:0; padding:0;">
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="center" style="padding:20px 0;">
<!-- Container -->
<table role="presentation" width="600" cellpadding="0" cellspacing="0" border="0" style="border:1px solid #dddddd;">
<tr>
<td style="padding:20px; font-family:Arial, sans-serif; font-size:16px; line-height:1.5;">
<!-- Email content here -->
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>Notes:
- Outer table is full width, used to center the inner container.
- Inner table uses a fixed width, for example 600 pixels, which is common for emails.
role="presentation"tells screen readers that this table is only for layout.
Rule: Use <table> based layouts for HTML emails, not flexbox or CSS grid. This is crucial for compatibility.
Styling HTML Emails Safely
Inline Styles
Many email clients strip out <style> blocks or ignore some CSS sources. The most reliable way to apply styles is with the style attribute.
Bad (may be ignored):
<head>
<style>
.button {
background: #4CAF50;
}
</style>
</head>
<body>
<a href="..." class="button">Click</a>
</body>Better:
<a href="https://example.com"
style="background:#4CAF50; color:#ffffff; padding:10px 20px; text-decoration:none; border-radius:4px; display:inline-block;">
Click
</a>This is verbose, but works across more clients.
Commonly Supported CSS Properties
Safe to use in most clients:
| Category | Examples |
|---|---|
| Text | font-family, font-size, font-weight, color, line-height |
| Box model | padding, margin (limited), border, background-color |
| Display/layout | display:block, display:inline-block, text-align, vertical-align |
| Images | width, height, border-radius (partially) |
Risky or often unsupported:
| Feature | Notes |
|---|---|
| Flexbox | Poor support, especially in Outlook |
| CSS Grid | Poor support |
position | Often ignored |
| Web fonts | Limited support, require fallbacks |
| Complex media queries | Not supported in many desktop clients |
When unsure, test or check email CSS support tables (for example, caniemail.com).
Use System Fonts
Web fonts are not guaranteed to load. Use a stack of safe fonts:
<span style="font-family: Arial, Helvetica, sans-serif; font-size:16px;">
Hello from our app!
</span>Creating a Simple HTML Template
Here is a very small but realistic HTML email for a password reset.
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Password reset</title>
</head>
<body style="margin:0; padding:0; background-color:#f4f4f4;">
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="center" style="padding:20px 0;">
<table role="presentation" width="600" cellpadding="0" cellspacing="0" border="0" style="background-color:#ffffff; border-radius:4px; overflow:hidden;">
<!-- Header -->
<tr>
<td style="background-color:#2b6cb0; padding:16px 24px; color:#ffffff; font-family:Arial, sans-serif; font-size:20px;">
Example App
</td>
</tr>
<!-- Body -->
<tr>
<td style="padding:24px; font-family:Arial, sans-serif; font-size:16px; color:#333333; line-height:1.5;">
<p style="margin:0 0 16px 0;">Hi {{ user_name }},</p>
<p style="margin:0 0 16px 0;">
We received a request to reset your password. Click the button below to choose a new one.
</p>
<p style="margin:0 0 24px 0; text-align:center;">
<a href="{{ reset_link }}"
style="background-color:#2b6cb0; color:#ffffff; text-decoration:none; padding:12px 24px; border-radius:4px; display:inline-block; font-weight:bold;">
Reset your password
</a>
</p>
<p style="margin:0 0 16px 0; font-size:14px; color:#666666;">
If you did not request a password reset, you can ignore this email.
</p>
<p style="margin:0; font-size:14px; color:#666666;">
Thanks,<br>Example App Team
</p>
</td>
</tr>
<!-- Footer -->
<tr>
<td style="background-color:#f4f4f4; padding:12px 24px; text-align:center; font-family:Arial, sans-serif; font-size:12px; color:#999999;">
© {{ year }} Example App. All rights reserved.
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>
Dynamic parts, like {{ user_name }}, {{ reset_link }} and {{ year }}, will be filled by your backend template system.
Buttons and Call‑To‑Action Links
Button as a Styled Link
Most email buttons are just <a> tags with styles:
<a href="{{ verify_link }}"
style="background-color:#38a169; color:#ffffff; text-decoration:none; padding:12px 30px; border-radius:4px; display:inline-block; font-family:Arial, sans-serif; font-size:16px;">
Verify your email
</a>
You can center it using a containing <p> with text-align:center.
Bulletproof Buttons with Tables
Some clients handle inline styles inconsistently on <a>. You can use a button built from a table cell.
<table role="presentation" cellpadding="0" cellspacing="0" border="0" align="center">
<tr>
<td bgcolor="#3182ce" style="border-radius:4px;">
<a href="{{ action_link }}"
style="display:inline-block; padding:12px 24px; font-family:Arial, sans-serif; font-size:16px; color:#ffffff; text-decoration:none;">
Confirm your account
</a>
</td>
</tr>
</table>This is more verbose, but tends to be more reliable.
Using Images in HTML Emails
Inline Images vs External URLs
Most of the time you will host images on a server and reference them with src URLs:
<img src="https://cdn.example.com/email/logo.png"
alt="Example App logo"
width="120"
style="display:block; margin:0 auto 16px auto;">Important points:
- Always include
alttext. Many clients block images by default. - Specify
widthand possiblyheightso layout is stable even when images are blocked. - Use HTTPS URLs.
Avoid Background Images
Background images in CSS are often not supported. Prefer regular <img> elements.
Bad:
<td style="background-image:url('https://...');">
...
</td>
Better: just use an <img> tag at the top of a cell.
Logo Example
A header with a logo:
<tr>
<td style="padding:20px; text-align:center; background-color:#1a202c;">
<img src="https://cdn.example.com/logo-email.png"
alt="Example App"
width="140"
style="display:block; margin:0 auto;">
</td>
</tr>Making HTML Emails Responsive
Many recipients read emails on phones. A 600‑pixel fixed width layout is standard, but on small screens you want text to remain readable.
Full responsive design can be complex in emails and heavy use of media queries may not work everywhere. For beginners, focus on:
- Single column layouts
- Larger font sizes, at least 14px to 16px
- Buttons that are easy to tap, for example at least 44px high
Simple example with a safe width:
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="center">
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" style="max-width:600px;">
<tr>
<td style="padding:16px; font-family:Arial, sans-serif; font-size:16px;">
Content
</td>
</tr>
</table>
</td>
</tr>
</table>
Here max-width:600px lets the email shrink nicely on narrow screens.
Rule: Prefer simple, single column layouts with large fonts and clear buttons. Complex multi‑column responsive layouts are hard to make reliable in emails.
Dynamic Content and Templating
In a backend application you will rarely write raw HTML with actual values. Instead, you create a template with placeholders.
Example for a “welcome” email template, using a generic template syntax:
<p style="font-family:Arial, sans-serif; font-size:16px;">
Hi {{ user_name }},
</p>
<p style="font-family:Arial, sans-serif; font-size:16px;">
Welcome to Example App! Click the button below to get started.
</p>
<p style="text-align:center;">
<a href="{{ onboarding_link }}"
style="background-color:#2b6cb0; color:#ffffff; text-decoration:none; padding:12px 24px; border-radius:4px; display:inline-block;">
Go to your dashboard
</a>
</p>Your backend language and template engine will:
- Load this HTML file as a template.
- Replace
{{ user_name }}and{{ onboarding_link }}with real values. - Send the final HTML string through your email sending code.
Accessibility and Text‑Only Fallbacks
HTML emails should still be readable if:
- Styles are removed
- Images are blocked
- The user uses a screen reader
A few practices help:
- Use semantic tags like
<p>,<h1>for important headings. - Provide
alttext for images, for example"Order receipt"for a banner image. - Avoid using text embedded inside images as the only way to convey information.
- Make sure the HTML email still makes sense as plain text.
Plain text version example for the earlier password reset email:
Hi {{ user_name }},
We received a request to reset your password.
Reset your password by opening this link:
{{ reset_link }}
If you did not request a password reset, you can ignore this email.
Thanks,
Example App TeamCommon Pitfalls and Gotchas
Here are typical mistakes when creating HTML emails:
| Mistake | Problem |
|---|---|
| Using modern CSS layout only | Layout breaks in Outlook and older clients |
Putting all styles in <style> only | Styles may be stripped or ignored |
| No plain text version | Worse deliverability and bad experience in some clients |
| Relying only on images for content | Content invisible when images are blocked |
| Very wide content (full‑width 1200px) | Hard to read on mobile, horizontal scrolling |
Forgetting alt attributes | Screen readers and blocked images show nothing useful |
| Using JavaScript | JavaScript is usually removed and is also a security risk |
Rule: Do not use JavaScript in HTML emails. It is stripped or blocked by almost all email clients.
Reusable Patterns for Application Emails
You can design basic patterns and reuse them across many emails.
Common Layout Blocks
- Header
Contains logo and maybe application name. - Body
- Greeting: “Hi {{ user_name }},”
- Main message paragraph
- Call‑to‑action button
- Additional information or instructions
- Footer
- Copyright info
- Company address (for legal reasons in many countries)
- “You received this email because …” text
Example footer:
<p style="margin:0; font-family:Arial, sans-serif; font-size:12px; color:#999999; text-align:center;">
You received this email because you signed up for Example App.
</p>
<p style="margin:4px 0 0 0; font-family:Arial, sans-serif; font-size:12px; color:#999999; text-align:center;">
© {{ year }} Example App, Inc. 123 Example Street, Example City
</p>You can extract these repeated sections into separate templates in your backend, and include them in each email template.
Summary
HTML emails are constrained mini web pages that must:
- Use table‑based layouts
- Use mostly inline CSS
- Avoid JavaScript and advanced CSS features
- Provide text‑only fallbacks
- Be simple, readable, and robust
With these patterns, your backend can generate HTML emails for verification, password resets, order receipts, and many other common flows.
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!