33.10. Where to Go Next
Table of Contents
Growing Beyond This Course
You have a solid foundation. The next step is to turn that foundation into real, valuable backend skills through deliberate practice, smart learning, and real projects.
This chapter will show you practical paths you can follow after finishing this course. Think of it as a map of possible next steps, not a strict checklist.
Clarify Your Direction
Before choosing what to learn next, decide what you want in the short term. For example:
| Goal | What to Focus On Next |
|---|---|
| Get a junior backend job | Strong portfolio, solid Python + FastAPI + SQL, testing, Git, basic Docker |
| Freelance / small clients | Simple REST APIs, deployment to cheap servers, documentation, reliability |
| Eventually become an architect | Deep understanding of databases, architecture patterns, distributed systems |
| Work in a product startup | Full cycle: backend, basic frontend, CI/CD, monitoring, cloud basics |
| Contribute to open source | Git, GitHub workflows, reading other people’s code, communication |
You can change direction later. For now, pick a primary goal so you can choose your next steps intentionally.
Deepen Your Core Backend Skills
You already know basics: HTTP, REST, Python, FastAPI, PostgreSQL, Docker, testing. To become strong, you need depth and fluency.
1. Master Your Main Language (Python)
Aim to move from “I can make it work” to “I can design it well.”
Focus areas:
- Python internals at a practical level
- How lists, dicts, and sets behave in terms of time complexity
- Mutability and immutability
- Generators and iterators
- Comprehensions and context managers
- Advanced language features
- Typing:
Protocol,TypedDict,Final,Literal dataclassesvs normal classes- Decorators and descriptors (only what you really need)
- Async and
asynciopatterns in real applications - Code quality
- Use
mypyor another type checker on real projects - Use linters like
rufforflake8 - Follow PEP 8 and consistent formatting with
black
Practical practice:
- Take one of your project’s modules and:
- Add type hints everywhere
- Run a type checker and fix all errors
- Refactor long functions into small, clear ones
- Rewrite a simple script in:
- Sync version
- Async version
Compare readability and performance.
2. Learn One Web Framework Deeply
You used FastAPI. Becoming strong means:
- Read the official FastAPI docs end to end, slowly
- Build at least two non-tutorial projects with FastAPI that you design yourself
- Explore:
- Dependency injection in more complex scenarios
- Background tasks at scale
- Custom middleware
- Error handling patterns
- Custom authentication / authorization dependencies
You do not need to learn every framework. One deep framework knowledge is worth more than shallow knowledge of three.
3. Understand Databases in Practice
Move from “I know SQL syntax” to “I can design, debug, and optimize.”
Practice:
- Design schemas for different domains:
- Blog, CRM, chat app, analytics app
- For each:
- Identify primary and foreign keys
- Decide which columns need indexes
- Write queries for:
- Pagination
- Filtering and sorting
- Simple reports with
GROUP BY
Learn to use the database itself:
- Use
EXPLAINin PostgreSQL to inspect queries - Practice:
- Optimizing a slow query
- Adding and removing indexes and measuring impact
- Dealing with N+1 query problems when using an ORM
Expand Toward Real-World Backends
Once your core is stronger, you can move into the areas that make backends production ready.
4. Cloud Platforms
Pick one major cloud:
- AWS (most common in companies)
- GCP
- Azure
For a first backend job, you do not need to know everything about cloud. Focus on:
- Compute:
- EC2 (AWS), or similar virtual machines
- Maybe a managed container service later (ECS, EKS)
- Storage and databases:
- Managed PostgreSQL (RDS, Cloud SQL, etc.)
- Object storage (S3 and equivalents)
- Networking basics:
- Security groups or firewalls
- Load balancers at a conceptual level
Do one concrete mini project:
- Deploy a simple FastAPI app on a cloud VM
- Use managed PostgreSQL
- Serve through a domain using HTTPS
This connects many things you learned in the course in a real environment.
5. CI/CD in Practice
Turn your projects into something that automatically builds, tests, and can deploy.
Start small:
- Use GitHub Actions or GitLab CI:
- Run tests on every push
- Run linters
- Add a job that builds your Docker image
- Later, add an environment:
- A “staging” deployment from a
developbranch - A “production” deployment from
mainor a release tag
What you gain:
- Employers see you can work with real workflows
- Your own projects are easier to maintain
- You learn how professional teams ship code
6. Observability and Reliability
Most beginners ignore this. It will set you apart.
Pick one of your bigger projects and:
- Add structured logging:
- Log a JSON object for each request with: path, method, duration, user id (if any), status code
- Add metrics:
- Request count per endpoint
- Error rate
- Database query duration
Use:
- Prometheus + Grafana locally with Docker
- Or a cloud monitoring service if you deploy to the cloud
Set at least one alert condition in your mind:
Rule: A backend is not "production ready" if it has no logging, no monitoring, and no way to know when it breaks.
Even if you only do this locally, you will understand how real teams think about uptime.
Choose Your Specialization Direction
Over time you may want to specialize. You do not need to choose right now, but here are common directions and what they typically require.
| Direction | What You'll Likely Focus On |
|---|---|
| API-centric backend engineer | REST, GraphQL, API gateways, rate limiting, auth, documentation, integration testing |
| Data-heavy / analytics backend | Complex SQL, ETL, OLAP, warehouses, batch jobs, performance tuning |
| Reliability / DevOps oriented | Linux, Docker deeply, Kubernetes, CI/CD, observability, incident response |
| Security focused | Auth systems, OAuth2/OIDC, secure coding, penetration testing basics, compliance awareness |
| Realtime / high throughput | Asynchronous patterns, WebSockets, queues, distributed systems, caching strategies |
Explore each direction by:
- Building 1 or 2 focused mini projects per area
- Reading job descriptions for that role to see what is expected
Build a Strong Portfolio
Your portfolio is often more important than your certificates.
Aim for:
- 3 to 5 solid, small to medium projects
- Each project shows specific skills, not just a “CRUD again” repetition
Examples:
| Project Idea | What It Demonstrates |
|---|---|
| Task Management API (from this course, improved) | REST, auth, pagination, testing, docs |
| URL Shortener | Hashing, database design, redirection, rate limiting |
| Simple E-commerce backend | Products, carts, orders, payments (test mode), background jobs |
| Real-time chat or notifications | WebSockets, async processing, Redis pub/sub |
| Analytics service for another app | ETL, aggregation queries, reporting endpoints |
To strengthen each project:
- Add documentation:
- README with setup, features, and API description
- OpenAPI documentation via FastAPI built-in tools
- Add tests:
- Show test coverage badge if you like
- Include unit and integration tests
- Add deployment:
- Docker setup
- At least one demo deployment, even on a cheap VPS or free tier
This turns projects from “just code” into “almost production ready”.
Learn From Other People's Code
Reading good code is as important as writing your own.
Where to look:
- Popular FastAPI or Django open source projects on GitHub
- Libraries you use daily: look inside their source
- Well-structured templates and boilerplates
How to practice:
- Pick a small repository.
- Try to answer:
- How is the project structured?
- Where are API endpoints defined?
- How is configuration loaded?
- How are tests organized?
- Take one idea and apply it to your own project:
- Maybe a better folder structure
- Or a better configuration mechanism
This builds your mental library of patterns.
Practice Real Collaboration
Backend work is rarely solo. You need to work with others and with existing code.
Ways to practice:
- Contribute to open source:
- Start with documentation or small bug fixes
- Learn how to open issues and pull requests
- Respond to code review comments
- Pair programming:
- Work with a friend or another learner
- Take turns: driver (typing) and navigator (thinking out loud)
- Simulate a team project:
- Use branches, pull requests, and code reviews even if you are alone
- Write issues for yourself in the repo’s issue tracker
This builds the habits companies expect.
Keep Your Knowledge Current
Technology changes, but the core concepts stay valuable. Focus on both.
Permanent skills
These rarely go out of date:
- HTTP, TCP/IP, DNS
- Relational database design and SQL
- Clean code, testing, and architecture fundamentals
- Linux basics and shell scripting
- Understanding of performance and scalability
Things that change faster
These change but are still important:
- Framework versions and features
- Cloud services and pricing models
- Popular tools in CI/CD and observability
Strategy:
- Spend more time deepening permanent skills
- For fast-changing tools:
- Learn one solid stack well
- Be willing to adapt tools later, based on job requirements
Suggested Learning Roadmaps
Here are a few concrete paths you could follow next, each roughly 3 to 6 months of part-time learning.
Roadmap A: Job-ready Backend Generalist
- Month 1–2
- Strengthen Python and FastAPI
- Build 2 serious FastAPI projects, with:
- Auth
- Pagination
- Validations
- Tests
- Month 2–3
- PostgreSQL in depth:
- Indexing, transactions, query analysis
- More complex queries and joins
- Add proper Docker setups for your projects
- Month 3–4
- Learn basic cloud deployment:
- Deploy one project on a cloud VM
- Use managed PostgreSQL
- Configure HTTPS and a domain
- Month 4–6
- CI/CD for at least one project
- Add logs, metrics, and monitoring locally
- Polish portfolio and start applying for jobs
Roadmap B: API & Integrations Specialist
- Master REST deeply
- Pagination, filtering, searching patterns
- Idempotency and error handling patterns
- API versioning and documentation
- Learn GraphQL basics
- Build a small GraphQL API
- Understand when to use GraphQL vs REST
- Focus on security
- OAuth 2.0, OpenID Connect
- JWT, access and refresh tokens
- API keys, rate limiting
- Practice integrations
- Integrate with 3rd party APIs:
- Payments (e.g. Stripe test mode)
- Email providers
- Webhooks (consume and produce)
Roadmap C: Reliability/DevOps oriented Backend
- Gain strong Linux and Docker skills
- Learn infrastructure as code (e.g. Terraform, Ansible basics)
- Work with Kubernetes at least locally (kind, minikube)
- Focus on observability
- Prometheus, Grafana, log aggregation tools
This path suits you if you enjoy systems, operations, and making things stable at scale.
Track Your Progress and Avoid Burnout
Learning backend development is a long journey. To make it sustainable:
- Set small, weekly goals:
- “Add tests for 3 endpoints”
- “Deploy one small change using CI/CD”
- Review monthly:
- What did I actually build?
- Which concepts do I still find confusing?
- Keep a log:
- Short daily or weekly notes:
- What you learned
- What you broke and how you fixed it
This helps you see progress when motivation drops.
How to Ask for Help Effectively
Whether online or in a team, your ability to ask questions well is a skill.
When asking for help:
- Include:
- What you tried
- Expected behavior
- Actual behavior
- Relevant errors and code snippets
- Reduce the problem:
- Create a minimal reproducible example
- Often, you solve the problem while trying to shrink it
This is useful in:
- GitHub issues
- Stack Overflow
- Company Slack or Teams channels
Good questions lead to good answers and show professionalism.
Putting It All Together
You now have:
- A foundation in backend concepts and tools
- A set of projects you can improve and expand
- Several possible directions to specialize in
Your next steps:
- Pick a primary goal for the next 3–6 months.
- Choose a roadmap that aligns with that goal, or adapt one.
- Commit to building real, finished things:
- With tests
- With documentation
- With some level of deployment
If you keep building, refactoring, and learning from real code, you will move from “course graduate” to “backend engineer” in a very real, practical sense.
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!