How phucptit2003/ungdunggiaodoan works
Project type and purpose
• From the README (“Food delivery application”), this is a full-stack, multi-tenant e-commerce/mobile application enabling users both to list products for sale and to place orders from other sellers. Future requirements include order tracking.
(minimal) file structure
• While only README.md and Ý tưởng.txt are provided, the domain suggests a typical web/mobile app structure with separate front-end, back-end, data storage, and integrations. We will assume a layered or microservices-style backend to cover core domains: authentication, product/catalog, ordering, and tracking.
README for additional insights
• Key features: user registration (buyers, sellers), product listing, order placement, online/offline availability, and planned order-tracking capabilities.
• Implied technical stack: likely React/Vue Native or Flutter mobile apps + single-page web app + REST or GraphQL API + relational database + real-time tracking.
Detail
• Microservice as its own component.
• Asynchronous vs. synchronous flows.
• Cross-cutting infrastructure: load balancer, CDN, monitoring (Prometheus/Grafana), logging (ELK).
• Don’t overthink—represent every domain slice (Auth, Catalog, Order, Tracking, Notifications) separately to maximize clarity.