How tough-dev-school/education-backend works
Main Components
• Web/API Server: Represent the Django application acting as a WSGI server (or ASGI if applicable). It handles HTTP requests from clients (the frontend, which is a vue.js application in a separate repo).
• Core/Configuration Layer: Include the “core” component that holds global settings, configurations, integrations (e.g., payment integrations, third-party APIs), middleware, and shared utility functions.
• Database: Indicate Postgres as the central relational database (configured via docker-compose).
• Redis/Cache and Celery Tasks: Show the caching layer and message broker (Redis) that support background workers (Celery) – as indicated by the celery.py file and tasks directories in “src/core/tasks.”
• External Integrations: Create external components for payment gateways (Tinkoff, Stripebank, banking), email/messaging services (Dashamail, Postmark), file storage (S3), and notifications (Telegram). These should be depicted outside of the main application boundaries and connected via integration service modules.
Architectural Patterns and Design Principles
• Modular and Domain-Driven Organization: Emphasize that the design splits the application into many self-contained Django apps (each with its own models, migrations, tests, services, and API endpoints). This encapsulation supports clear separation of concerns.