Best practices for structuring Django REST APIs for maintainability and scalability
I am building a Django-based backend for an e-commerce project with multiple models and REST API endpoints.
I want to follow clean architecture and maintainability best practices.
How should I structure views, serializers, and URLs for scalability and easier debugging?
Tags: Python, Django, REST-API, Backend
It is always better to separate the applications (users/payment/categories etc) and keep its core logic inside itself.
I think for a big project it is not good to put all the models, serializers or urls into a single module named api.