leanlag87/catfecito-pern

Purpose and entry points

CatFecito is a serverless ecommerce system: a React/Vite client consumes an AWS API Gateway-backed Lambda API for catalog, accounts, carts, orders, administration, and payments. Client bootstraps at client/src/main.jsx, composes global UI/auth providers in client/src/app/providers/AppProviders.jsx, and selects pages/guards through client/src/app/routes/AppRoutes.jsx. Backend deployment and HTTP/resource topology begin at serverless.yml.

Client application shell and access control

The SPA owns navigation, protected routes, modal state, and inactivity behavior. Authentication state and role checks are feature-local, while route guards constrain user/admin screens before their data flows execute.

• client/src/features/auth/stores/authStore.js

• client/src/features/auth/hooks/useRequireRole.js

• client/src/app/routes/routeGuards.jsx

Client domain feature boundary

Each major ecommerce domain follows a UI → hooks → service → client-side store pattern. Product browsing/filtering, cart mutation, checkout/order tracking, profiles, and administration are independent feature modules, limiting cross-domain UI coupling.

• client/src/features/products/services/products.service.js

• client/src/features/cart/stores/cartStore.js

• client/src/features/orders/hooks/useOrderCheckout.js

API integration flow

Feature services call a shared HTTP abstraction, configured with API endpoints and environment-derived connectivity. API responses update feature stores and render components; authenticated calls carry the client’s auth context/token. This is the boundary between browser state and the serverless backend.

• client/src/config/apiClient.js

• client/src/config/apiEndpoints.js

• client/src/services/api.js

Lambda API and layered business logic

API Gateway invokes discrete Node.js Lambda handlers. Handlers delegate to services for business rules, then repositories for DynamoDB access, preserving a clear controller/service/data boundary. The Serverless configuration splits endpoint registrations by domain and defines provider concerns such as HTTP API, IAM, CORS, DynamoDB, and S3.

• server/functions/users/orders/createOrder.js

• server/services/order.service.js

• server/repositories/order.repository.js

Identity, authorization, and administration

Registration/login integrate JWT and AWS Cognito helpers; an authorizer protects authenticated API routes. Admin handlers/services separately govern product, category, user, and order management, enforcing the privileged control-plane boundary.

• server/functions/auth/authorizer.js

• server/services/auth.service.js

• server/services/admin/order.service.js

Commerce transaction and payment lifecycle

A customer cart is persisted through cart handlers/services/repository; order creation turns checkout intent into an order, then payment preference creation delegates to MercadoPago. MercadoPago calls the webhook, which queries/updates payment state and the associated order. DynamoDB atomic transactions are the core consistency mechanism; payment handling is an external asynchronous boundary.

• server/functions/users/cart/addToCart.js

• server/functions/payments/createPreference.js

• server/functions/payments/webhook.js

Runtime, infrastructure, and delivery

The backend runs Node.js 20.x on AWS Lambda behind API Gateway, uses DynamoDB for application data, S3 for product images, Cognito for identity, MercadoPago for payment processing, and CloudWatch logging. The React app is containerized and served by Nginx; environment-specific Docker Compose and GitHub Actions pipelines support dev, staging, and production delivery.

• docker/client/Dockerfile

• docker/client/nginx.conf

• .github/workflows/cd-prod.yml