How m0hit5/django-ecommerce works
Project Type and Purpose
• This is a monolithic Django-based full-stack e-commerce web application.
• Key features: user accounts, product categories, shopping cart, orders, payments, reviews, email notifications, static/media asset management.
• Deployed on AWS Elastic Beanstalk (EB), likely using RDS (PostgreSQL/MySQL), S3 for media, and SMTP for email.
Main Architectural Tiers
A. Presentation Layer (Client)
– Web browser or mobile client
– Static assets (CSS, JS, fonts, images) delivered via CDN or EB’s static file host
B. Application Layer (Django Monolith)
– WSGI/ASGI server (Gunicorn/Uvicorn) running Django project “greatkart”
– Django apps as logical sub‐components:
• accounts (authentication, profiles, email verification)
• store (product listing, variations, gallery, reviews)
• category (product categorization, context processors)
• carts (add/remove items, context data)
• orders (checkout, payment processing, order lifecycle, invoices)
– Templates & Context Processors for dynamic HTML generation
C. Data Layer
– Relational Database (PostgreSQL/MySQL) for models in each app
– File Storage (AWS S3 or local MEDIA_ROOT) for product images, user avatars
D. External Services
– SMTP Email Service (Gmail SMTP or AWS SES) for order notifications, password resets
– Payment Gateway (Stripe/PayPal) invoked in orders/forms and views
– AWS Elastic Beanstalk for hosting, ELB/ALB for load balancing, Auto Scaling
Component Relationships & Data Flow
1. Client → Load Balancer → WSGI/ASGI Server
2. WSGI/ASGI → Django URL Router → App Views → Business Logic (models/forms)
3. Business Logic ↔ Database (ORM)
4. Business Logic ↔ File Storage (media files)
5. Views → Templates → HTML → Client
6. Cart updates, order placements trigger:
– Database writes (CartItem, Order, OrderProduct)
– Email Service call (send_mail)
– Payment Gateway API call
7. Static files served directly from CDN/S3
Architectural Patterns & Design Principles
• MVC (MTV) pattern via Django’s Model–Template–View separation
• Modular “apps” structure: each domain (accounts, store, carts, orders, category) encapsulates its own models, views, URLs, templates
• Context processors for injecting cart and category data into all templates
• Settings module for environment (SECRET_KEY, DEBUG, email credentials)
• Migrations for schema evolution