How shaharmeer/portfolio works
Main Components
• Django Web Server: Representing the core of your application. Include components such as:
• Django Application “myapp” (controllers in views.py, models, URLs, and templates for the user interface).
• The main project configuration in the “myceleryproject” directory (settings, WSGI, ASGI).
• Celery Components:
• Celery Worker: Executes tasks asynchronously (configured via myceleryproject/celery.py and defined tasks in myapp/tasks.py).
• Celery Beat Scheduler: Responsible for sending periodic tasks to the message broker.
• Database: SQLite (shown as “db.sqlite3” after migrations) used for storing application data.
Relationships and Interactions
• Interaction between Celery Beat and the message broker, noting that Celery Beat pushes scheduled task messages to the broker.
• Communication between the Celery Worker and the broker, illustrating that workers consume task messages from it.
Architectural Patterns and Technologies
• That the project employs the MVC (or MVT – Model, View, Template in Django) pattern, where:
• Models handle the data structure (myapp/models.py).
• Views (myapp/views.py) process requests.
• Templates (within myapp/templates/myapp) render the frontend.
• Microservice-like behavior for task processing: while Django handles standard synchronous web requests, Celery manages asynchronous background tasks.
• Dependencies like:
• Django for the web framework.
• Celery for task scheduling and distributed asynchronous processing.
• SQLite for database storage.
• And implicitly, a message broker (RabbitMQ/Redis) for Celery’s messaging (even if it is not explicitly set up in the provided file structure).
• Specify that the separation between components is key: distinguishing between synchronous operations (handled by Django) and asynchronous processing (handled by Celery).
• Use of configuration files (like myceleryproject/celery.py and Django’s settings.py) which are pivotal in linking the Django server to the Celery system.
• Deployment scripts (e.g., manage.py, migration steps) as side-notes to illustrate initialization and startup procedures, but keep the focus on the overall architecture.