You're reading from Django in Production

Product type Book

Published in Apr 2024

Publisher Packt

ISBN-13 9781804610480

Pages 348 pages

Edition 1st Edition

Languages

Python

Concepts

Server Side Web Development

Author (1):

Arghya Saha

Table of Contents (21) Chapters

Preface

1. Part 1 – Using Django and DRF to Build Modern Web Application

2. Chapter 1: Setting Up Django with DRF

3. Chapter 2: Exploring Django ORM, Models, and Migrations

4. Chapter 3: Serializing Data with DRF

5. Chapter 4: Exploring Django Admin and Management Commands

6. Chapter 5: Mastering Django Authentication and Authorization

7. Part 2 – Using the Advanced Concepts of Django

8. Chapter 6: Caching, Logging, and Throttling

9. Chapter 7: Using Pagination, Django Signals, and Custom Middleware

10. Chapter 8: Using Celery with Django

11. Chapter 9: Writing Tests in Django

12. Chapter 10: Exploring Conventions in Django

13. Part 3 – Dockerizing and Setting Up a CI Pipeline for Django Application

14. Chapter 11: Dockerizing Django Applications

15. Chapter 12: Working with Git and CI Pipelines Using Django

16. Part 4 – Deploying and Monitoring Django Applications in Production

17. Chapter 13: Deploying Django in AWS

18. Chapter 14: Monitoring Django Application

19. Index

Why subscribe?

20. Other Books You May Enjoy

Introducing the different types of tests in software development

All of us developers love to write code and build systems and applications. All of us hate attending meetings. Another thing most developers hate is writing tests. We all have been there. When I started my career, and whenever I was asked by my senior/mentor to write test cases for code, I would dread the thought. It would take almost double the time to write test cases for the code than it took to build the feature.

But tests are a necessary evil, and now that I am a senior engineer building dozens of scalable systems, I always prefer to write tests for any project I work on. This gives me the confidence to ship my code to production without the fear of breaking the existing system, and this helps in the faster shipping of features.

When we build new features, we always test the code manually. For example, if I had to write code to find out whether a number is prime or not, I would write the code and then pass...