How realsuayip/django-sozluk works
Main Components
a. Frontend Layer:
• Static files (CSS, JS, templates)
• User interface components
• GraphQL client integration
b. Backend Layer:
• Django application server
• GraphQL API (dictionary_graph)
• Celery task queue
• Authentication system
• Admin interface
c. Infrastructure:
• Nginx reverse proxy
• PostgreSQL database
• Docker containers
• Cache layer (Redis/Memcached, implied by cached_db.py)
[Client Layer]
• ↓ ↑
[Load Balancer Layer (Nginx)]
• ↓ ↑
[Application Layer]
• ↓ ↑
[Data Layer]
Component Details
a. Client Layer:
• Browser/mobile clients
• Static assets (dictionary/static/)
• Template rendering (dictionary/templates/)
b. Load Balancer Layer:
• Nginx configuration (conf/nginx.conf)
• SSL termination
• Static file serving
c. Application Layer:
• Django Web Application
• URL routing (dictionary/urls/)
• Views (dictionary/views/)
• Forms (dictionary/forms/)
• GraphQL API (dictionary_graph/)
• Celery Worker
• Admin Interface
d. Data Layer:
• PostgreSQL Database
• Cache Store
• File Storage (for images)
Key Relationships to Highlight
• Authentication flow
• GraphQL API interactions
• Database access patterns
• Caching layer interactions
• Task queue workflow
Deployment Context
Two configurations:
• Development environment (docker/dev/)
• Production environment (docker/prod/)
Additional Elements
• Version information
• Scaling points
• Security boundaries
• Backup systems
Remember to indicate the Docker container boundaries and how they interact in the production environment, as this is a containerized application with distinct services for web, database, and nginx.