How huanglinbao/thriftstore works
Project type and purpose
• This is a full-stack web application called “Thrift Store,” a local e-commerce marketplace.
• Frontend: React SPA in the FrontEnd/ directory.
• Backend/API: Node.js + Express in the ThriftStoreApi/ directory.
• Database & storage: SupaBase (PostgreSQL-compatible DB, auth, file storage).
• CI/CD: Azure DevOps (mentioned in README).
File structure
• Top-level folders:
• FrontEnd/ – React code, public assets, components, styles.
• ThriftStoreApi/ – Express controllers, database connection, server entrypoints.
• ArchetictureDesign/ – existing architecture notes (can be referenced).
• Backend follows an MVC-style pattern: controllers folder, databaseConnection.js, server.js.
• No nested microservices—just one monolithic API.
• Configuration/build: package.json in both FrontEnd and ThriftStoreApi, plus lint/prettier files at root.
README
• Confirms tech stack: React JS, NodeJS + Express, SupaBase, Azure DevOps.
• Describes three user roles (guest, customer, admin) but no separate services per role.
Elements
• Browser → FrontEnd (initial load & subsequent API calls)
• FrontEnd → Express API (HTTP requests)
• Express API → SupaBase (DB & storage operations)
• Azure DevOps → FrontEnd / Express API (CI/CD deployments)
• Green for backend services,
• Orange for external services (SupaBase, Azure DevOps).