Commerce
E-Commerce & Marketplaces
Comprehensive guide to e-commerce platforms, marketplace systems, order management, catalog management, and online retail technology.
$6.3T
Global Market
$80B+
India Market
10M+
Daily Orders
75%+
Mobile Share
Understanding E-Commerce & Marketplaces— A Developer's Domain Guide
E-commerce encompasses all online buying and selling activities, from product discovery to checkout to delivery. Modern e-commerce platforms are complex ecosystems involving catalog management, inventory systems, pricing engines, order orchestration, payment processing, fulfillment, and customer experience layers. This domain covers B2C marketplaces, D2C brands, B2B commerce, and the technology that powers online retail.
Why E-Commerce & Marketplaces Domain Knowledge Matters for Engineers
- 1Global e-commerce market exceeds $6 trillion with 20%+ annual growth
- 2High-scale, high-availability systems processing millions of transactions
- 3Complex distributed systems with microservices architecture
- 4Rich product engineering opportunities - search, recommendations, personalization
- 5India's e-commerce growing at 25%+ CAGR, massive hiring
- 6Understanding seller systems, logistics integration, and fulfillment tech
How E-Commerce & Marketplaces Organisations Actually Operate
Systems & Architecture — An Overview
Enterprise E-Commerce & Marketplaces platforms are composed of a set of core systems, data platforms, and external integrations. For a detailed, interactive breakdown of the core systems and the step-by-step business flows, see the Core Systems and Business Flows sections below.
The remainder of this section presents a high-level architecture diagram to visualise how channels, API gateway, backend services, data layers and external partners fit together. Use the detailed sections below for concrete system names, API examples, and the full end-to-end walkthroughs.
Technology Architecture — How E-Commerce & Marketplaces Platforms Are Built
Modern E-Commerce & Marketplacesplatforms follow a layered microservices architecture. The diagram below shows how a typical enterprise system in this domain is structured — from the client layer through the API gateway, backend services, data stores, and external integrations. This is the kind of architecture you'll encounter on real projects, whether you're building greenfield systems or modernising legacy platforms.
End-to-End Workflows
Detailed, step-by-step business flow walkthroughs are available in the Business Flows section below. Use those interactive flow breakouts for exact API calls, system responsibilities, and failure handling patterns.
Industry Players & Real Applications
🇮🇳 Indian Companies
Flipkart
Marketplace
Java, React, Kubernetes
India's largest e-commerce, Walmart-owned
Amazon India
Marketplace + D2C
AWS, Java, React
Fastest growing market for Amazon globally
Myntra
Fashion E-commerce
React, Node.js, ML
Fashion marketplace, Flipkart subsidiary
Meesho
Social Commerce
Kotlin, React Native
130M+ transacting users, social selling
Nykaa
Beauty & Fashion
Custom Platform
Omnichannel beauty platform
Tata CLiQ
Luxury Marketplace
Salesforce Commerce
Tata Group's e-commerce platform
JioMart
Grocery & General
Custom, Java
Reliance's e-commerce arm
BigBasket
Grocery
Python, React
Online grocery, Tata-owned
🌍 Global Companies
Amazon
USAEverything Store
AWS, Java, React
World's largest e-commerce platform
Alibaba
ChinaMarketplace Giant
Custom, Java, AliCloud
Largest e-commerce by GMV globally
Shopify
CanadaE-commerce Platform
Ruby, React, GraphQL
Powers millions of online stores
eBay
USAMarketplace
Java, Node.js
C2C and B2C marketplace
Mercado Libre
LATAMMarketplace
Java, React
Largest e-commerce in Latin America
Zalando
EuropeFashion Platform
Kotlin, React
Europe's leading fashion platform
Coupang
KoreaE-commerce
Java, Kubernetes
Korea's largest e-commerce, Rocket Delivery
Sea/Shopee
SEAMarketplace
Golang, React
Largest in Southeast Asia
🛠️ Enterprise Platform Vendors
Shopify
Commerce Platform, Checkout, POS, Markets
Powers millions of merchants globally
Salesforce Commerce
B2C Commerce, B2B Commerce, Order Management
Enterprise commerce cloud
Adobe Commerce
Magento Commerce, Experience Platform
Open-source and enterprise commerce
BigCommerce
Open SaaS Commerce, Headless Commerce
Mid-market e-commerce platform
commercetools
Headless Commerce, MACH Architecture
API-first commerce platform
Fabric
Modular Commerce, OMS, PIM
Headless commerce modules
Vtex
Commerce Platform, Marketplace, OMS
Popular in Latin America
SAP Commerce
Hybris Commerce Suite
Enterprise omnichannel commerce
Core Systems
These are the foundational systems that power E-Commerce & Marketplaces operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What E-Commerce & Marketplaces Teams Actually Use. Every technology choice in E-Commerce & Marketplacesis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across E-Commerce & Marketplaces is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern E-Commerce & Marketplacesplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java/Spring Boot
Order management, inventory, catalog services
Node.js
API gateway, BFF services, real-time features
Golang
High-performance services - cart, checkout, pricing
Python
ML services - recommendations, search ranking, fraud
🖥️ frontend
React/Next.js
Web storefront, seller portal, admin dashboards
React Native/Flutter
Mobile shopping apps
GraphQL
Flexible data fetching for frontend
🗄️ database
PostgreSQL
Order data, customer data, transactional systems
MongoDB
Product catalog, reviews, flexible schema data
Elasticsearch
Product search, autocomplete, filters
Redis
Cart data, session cache, rate limiting
Apache Kafka
Event streaming, order events, inventory updates
🔗 integration
REST APIs
Service-to-service communication
gRPC
High-performance internal services
GraphQL Federation
Unified API for frontends
Webhooks
Seller integrations, logistics updates
☁️ cloud
AWS/GCP
Cloud infrastructure, auto-scaling
Kubernetes
Container orchestration, microservices
CDN (CloudFront)
Static assets, images, API caching
S3/GCS
Product images, media storage
Interview Questions
Q1.How would you design an e-commerce product catalog that handles millions of products?
Use a combination of relational (PostgreSQL) for structured data like pricing and inventory, and NoSQL (MongoDB) for flexible product attributes. Implement PIM (Product Information Management) for data governance. Use Elasticsearch for search with denormalized product data. Cache hot products in Redis. Implement product data versioning for audit. Use CDN for images. Design for multi-tenant if marketplace. Partition data by category for scale.
Q2.How do you handle inventory consistency during flash sales with millions of concurrent users?
Implement pessimistic locking at database level for inventory updates. Use Redis for real-time inventory counters with Lua scripts for atomic operations. Implement circuit breakers to handle traffic spikes. Use queuing (SQS/Kafka) to serialize inventory updates. Reserve inventory on add-to-cart with timeout-based release. Implement rate limiting per user. Use eventual consistency for analytics but strong consistency for purchases. Consider overselling buffer for popular items.
Q3.Explain how you would implement a recommendation engine for an e-commerce platform.
Combine collaborative filtering (users who bought X also bought Y) with content-based filtering (similar product attributes). Use user behavior signals - views, cart adds, purchases, search queries. Implement real-time recommendations using feature stores. Use ML models (matrix factorization, deep learning) trained on historical data. A/B test recommendation algorithms. Implement hybrid approach with fallback rules. Consider cold-start problem for new users/products. Personalize based on session context.
Q4.How do you ensure order consistency in a distributed microservices architecture?
Implement Saga pattern for distributed transactions across services (inventory, payment, order). Use compensating transactions for rollback. Event sourcing for order state changes. Idempotency keys to handle duplicate requests. Two-phase commit for critical paths. Dead letter queues for failed events. Implement order state machine with clear transitions. Use distributed tracing for debugging. Monitor for orphaned orders and implement reconciliation jobs.
Q5.How would you design a seller settlement system for a marketplace?
Track order events (delivered, returned, cancelled) in event store. Calculate settlement per seller factoring in commission, shipping subsidy, penalties. Implement T+N settlement cycle (typically T+7). Handle refunds and returns affecting settlement. Deduct TDS at source. Generate detailed settlement reports. Implement reconciliation with logistics and payment data. Handle disputes and adjustments. Comply with GST invoicing requirements. Use batch processing for large-scale settlements.
Q6.How do you optimize checkout conversion rate from a technical perspective?
Minimize checkout steps, implement one-page checkout. Prefetch user data (addresses, payment methods). Lazy load non-critical elements. Implement address autocomplete. Cache payment tokens for returning users. A/B test checkout flows. Implement cart persistence across devices. Optimize for mobile-first. Reduce payment failures with fallback methods. Implement abandoned cart recovery with notifications. Use analytics to identify drop-off points.
Glossary & Key Terms
SKU
Stock Keeping Unit - unique identifier for each distinct product variant
GMV
Gross Merchandise Value - total value of goods sold on the platform
AOV
Average Order Value - average amount spent per order
CAC
Customer Acquisition Cost - cost to acquire a new customer
LTV
Lifetime Value - predicted revenue from a customer over their lifetime
PDP
Product Detail Page - the page showing full product information
PLP
Product Listing Page - page showing list of products (search results, category)
OMS
Order Management System - system managing order lifecycle
WMS
Warehouse Management System - system managing warehouse operations
PIM
Product Information Management - system for managing product data
3PL
Third-Party Logistics - external logistics provider for fulfillment
D2C
Direct-to-Consumer - brands selling directly without intermediaries