How thesandeepkonda/aws-serverless-ecommerce-platform works
This is a serverless e-commerce backend: users and administrators call API Gateway routes handled by domain-specific Lambda functions for accounts, catalog, carts, orders, tracking, files, banners, and email. A typical purchase moves from cart management through checkout and payment verification to order persistence; the Orders service emits an OrderPlaced event that the Products handler consumes to decrement stock. The README is generic SAM setup guidance rather than product documentation, so capabilities and wiring here are based on the sampled handlers/services; unsampled subsystems are represented only where the tree supports them.
Main entry points: Orders/service.py Checkout and Orders · Products/lambda_handler.py Catalog API · Auth/lambda_handler.py Identity API · Auth/service.py Account and Login
Components 27
Commerce
- Cart API
services/Cart/lambda_handler.py - Cart Operations
services/Cart/service.py - Orders API
services/Orders/lambda_handler.py - Checkout and Orders
services/Orders/service.py - Catalog API
services/Products/lambda_handler.py - Product Catalog
services/Products/products_service.py - Catalog Features
services/Products
Identity
- Identity API
services/Auth/lambda_handler.py - Account and Login
services/Auth/service.py - Address Book
services/Auth/address.py - Admin Validation
services/Admin/lambda_handler.py
Operations
- Tracking API
services/History/lambda_handler.py - Order Tracking
services/History/service.py
Customer Experience
- Files and Banners API
services/Files/lambda_handler.py - File Operations
services/Files/service.py - Banner Management
services/Files/banners.py - Email API
services/Email/lambda_handler.py - Email Templates and Delivery
services/Email/service.py
External Services
- DynamoDB
- EventBridge
- Razorpay
- SMTP Server
- Google OAuth
- Object Storage
Other components
- Shopper
- Administrator
- API Gateway
Connections 34
- Shopper → API Gateway: sends requests
- Administrator → API Gateway: sends requests
- API Gateway → Cart API: routes cart calls
- Cart API → Cart Operations: dispatches operations
- Cart Operations → DynamoDB: reads and writes
- API Gateway → Orders API: routes order calls
- Orders API → Checkout and Orders: dispatches operations
- Checkout and Orders → DynamoDB: reads and writes
- Checkout and Orders → Razorpay: creates and verifies payments
- Checkout and Orders → EventBridge: publishes OrderPlaced
- EventBridge → Catalog API: dispatches OrderPlaced
- API Gateway → Catalog API: routes catalog calls
- Catalog API → Product Catalog: dispatches catalog calls
- Catalog API → Catalog Features: dispatches features
- Product Catalog → DynamoDB: reads and writes
- Catalog Features → DynamoDB: catalog data access
- API Gateway → Identity API: routes account calls
- Identity API → Account and Login: dispatches account calls
- Identity API → Address Book: dispatches address calls
- Account and Login → DynamoDB: reads and writes
- Address Book → DynamoDB: reads and writes
- Account and Login → Google OAuth: validates Google tokens
- API Gateway → Admin Validation: routes admin checks
- API Gateway → Tracking API: routes tracking calls
- Tracking API → Order Tracking: dispatches tracking calls
- Order Tracking → DynamoDB: reads and writes
- API Gateway → Files and Banners API: routes file calls
- Files and Banners API → File Operations: dispatches file calls
- Files and Banners API → Banner Management: dispatches banner calls
- File Operations → Object Storage: manages file objects
- Banner Management → DynamoDB: banner data access
- API Gateway → Email API: routes email calls
- Email API → Email Templates and Delivery: dispatches email calls
- Email Templates and Delivery → SMTP Server: sends mail