Designing a Scalable Cloud Shopping Cart: Architecture, Caching, and Payment Strategies
This article details the design and architecture of a cloud‑based shopping cart system, covering its functional modules, layered and cluster designs, technical goals such as stability and elasticity, three‑level caching, asynchronous checks, storage heterogeneity, and payment‑processing solutions.
Preface
Shopping cart main functions are: 1) similar to a traditional store, allowing users to select multiple items for checkout; 2) acting as a temporary wishlist; 3) providing a prime location for merchants to promote products.
Early Stage
ERP split; business service split; WCS split.
Shopping Cart Functional Module Overview
Layered Design
Interaction Layer : includes the shopping page (add to cart, view cart) and the checkout page (checkout, immediate purchase, submit order for payment).
Business Assembly Layer : provides the standard shopping‑cart workflow and non‑standard extensions.
Basic Service Layer : encapsulates data delivery from external systems and core service functions.
Cluster Design
From an application‑cluster perspective, the system is divided into two clusters: the cart cluster (high traffic, stores sensitive user purchase data) and the settlement cluster (stores additional, non‑sensitive information such as payment configuration).
Technical Architecture Design
The distributed design aims to achieve the following goals:
Stability: provide 24/7 reliable service. High Performance: ensure core services handle high concurrency with reliable response. Elasticity: enable smooth scaling of compute resources (e.g., VM, LXC) during traffic spikes. No Single Point of Failure: eliminate any single failure point in the system. Fault Masking Automation: automatically isolate and recover from network, application, or database failures.
Three‑Level Cache
Asynchronous Check
Storage Heterogeneity
Advantages: simple workflow.
Disadvantages: traffic spikes and high‑concurrency challenges.
Shopping Cart Payment Scheme
The payment middle‑platform adopts a heterogeneous solution:
Nginx+LUA aggregates front‑end business interfaces.
Anti‑scalper mechanisms.
Multi‑dimensional user feature identification.
These components together ensure secure, scalable, and efficient payment processing for the cloud shopping cart.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
ITFLY8 Architecture Home
ITFLY8 Architecture Home - focused on architecture knowledge sharing and exchange, covering project management and product design. Includes large-scale distributed website architecture (high performance, high availability, caching, message queues...), design patterns, architecture patterns, big data, project management (SCRUM, PMP, Prince2), product design, and more.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.