How emirbellos/cinema-project works
Core Components
• Frontend:
• Built using React.js (with Vite, Tailwind, and ESLint configurations).
• Contains pages and components handling the user interface (e.g., Home, Cartelera, Reservas, etc.).
• Communicates via REST APIs with the backend.
• Backend:
• Developed in Python (with Django as the web framework and Django REST Framework for API endpoints).
• Likely includes the core business logic for managing reservations.
• Although the file tree shows only a single Python file (Pruebapy.py), the README clearly specifies Django-based API services, so more backend modules would exist in the full project.
• Asynchronous Task Manager:
• Uses Celery for handling asynchronous processes (e.g., validating payment, reserving seats, sending confirmation emails).
• Connected to a message broker (RabbitMQ or Redis) as per the README.
• Database:
• PostgreSQL is used for storing persistent data (reservations, seats, users).
• External Services:
• Payment integration via third-party APIs (e.g., Stripe or PayPal).
• Notification services using platforms like SendGrid for sending confirmation emails.
• Deployment Infrastructure:
• Utilizes Docker Compose for managing multi-container configurations.
• Deployment on Azure with resources like a VM Linux instance, Azure Database for PostgreSQL, and monitoring/scaling enabled via services such as Azure Monitor.
Architectural Patterns and Design Principles
• Separation of concerns by showing distinct layers (Frontend vs. Backend vs. Infrastructure).
• Use of asynchronous processing for critical workflows (using Celery) and note that the system adheres to a service-oriented architecture.
• Mention RESTful API interactions between the frontend and backend.
• That the system is designed to be scalable and resilient, especially with the optional containerized deployment and cloud-based resources on Azure.