How leomssilva/ultimatespeedwarehc3 works
Project type and purpose
• This is a full-stack, low-code VTEX IO e-commerce application with a custom “combos” admin panel and a separate Node.js backend integrating AWS services and VTEX APIs.
• The front-end lives entirely on the VTEX IO platform (storefront + admin UI), while the backend is a standalone Node service running on AWS (EC2 or Lambda), using DynamoDB for storage and calling VTEX catalog/order APIs.
File structure
Top-level directories:
• server/ – Node.js service (index.js, AWS/Dynamo helper, VTEX API wrappers).
• web/ – VTEX IO app:
– react/ – custom React components and API‐calling services.
– store/ – VTEX JSON blocks for pages and components.
– styles/, assets/, admin/ – static assets, admin panel config, internationalization.
README
• Confirms VTEX IO usage, AWS EC2, Lambda, DynamoDB, VTEX APIs, Node/JS/TS tech stack.
• Mentions a “combos” admin panel (product‐bundle management).
Main components
A. Client layer
• Shopper (Storefront UI)
• Admin user (Combos panel in VTEX IO)
B. VTEX IO platform
• Storefront blocks & React components
• Admin panel app
• VTEX CDN & routing
C. Backend service
• Node.js service on AWS (EC2 or Lambda)
• AWS DynamoDB table (“combos”)
• VTEX API clients (catalog.js, order.js)
D. External services
• VTEX Catalog & Order APIs (via Axios)
• AWS services (EC2/Lambda, DynamoDB)
Relationships and data flows
1. Shopper requests storefront → VTEX IO serves static blocks + JS.
2. Storefront JS calls backend endpoint (/combos) → Node service.
3. Node service retrieves combo data from DynamoDB.
4. Node service may call VTEX Catalog/Order APIs to enrich combos.
5. Response flows back to storefront UI for rendering bundle suggestions.
6. Admin user opens Combos panel → React admin component.
7. Admin UI calls backend (CRUD endpoints) → Node service → DynamoDB.
Architectural patterns and design principles
• Layered separation: Front-end (VTEX IO) vs. backend (Node/AWS).
• Microservice style: Single-purpose combos service.
• Externalized configuration: .env for AWS, dynamic Axios config for VTEX.
• Code organization: service modules (catalog, order, config), util for UUIDs.