How bahtiyorjon05/paymeweb works
Project type and purpose
• This is a full-stack, cloud-hosted payment platform built with Django (Python) and a simple JavaScript/HTML/CSS frontend.
• It handles user authentication (2FA), card management, money transfers, currency conversion, transaction history, and provides an admin dashboard.
File structure and README
• Top-level files: LICENSE, README.md
• README lists:
• Backend: Python, Django, Django REST Framework (DRF)
• Frontend: HTML5/CSS3/JavaScript (server-rendered or static assets)
• Database: Azure SQL Database
• Cloud: Microsoft Azure (App Service, Container Registry)
• DevOps: Docker
• Security: JWT, CSRF
Main components
a. Client (Web Browser)
– Sends HTTP(S) requests, handles 2FA UI, transaction forms, dashboards, charts
b. Azure Front Door / Application Gateway (optional)
– SSL termination, WAF, global load balancing
c. Azure App Service (Container)
– Hosts the Dockerized Django application
d. Django Backend
– Django REST Framework endpoints
– Business logic for auth, payments, cards, currency conversion, reporting
– JWT and CSRF middleware
e. Azure SQL Database
– Stores users, cards, transactions, exchange rates, logs
f. External Services
– Real-time exchange-rate API
– (Optional) Email/SMS providers for 2FA, notifications
g. Azure Container Registry (ACR)
– Stores Docker images
h. CI/CD Pipeline
– GitHub/GitLab → build image → push to ACR → deploy to App Service
Interactions and data flow
1. User Browser → HTTPS → Azure Front Door/Gateway → App Service
2. App Service (Django) ↔ Azure SQL Database (queries & transactions)
3. Django Backend → External Exchange-Rate API (HTTP)
4. Django Backend → External 2FA SMS/Email API
5. CI/CD: Source Control → Build → ACR → Deployment
Architectural patterns and design principles
• Layered architecture: Presentation (frontend), Application (Django views/DRF), Persistence (Azure SQL)
• Stateless backend containers behind Azure App Service
• Secure by design: TLS at edge, JWT for API, CSRF protection
• Containerization for reproducibility & scalability
• Cloud-native: PaaS (App Service), managed SQL
Putting it all together
• Above or below, annotate the CI/CD flow: Git → Build → ACR → Deploy → App Service.