Backend Development 5 min read

Design and Architecture of a Cloud Shopping Cart System

This article explains the design and architecture of a cloud-based shopping cart system, covering its functional modules, layered and cluster designs, distributed goals such as stability and elasticity, three-level caching, asynchronous checks, heterogeneous storage, payment solutions, and anti‑scalping measures.

IT Architects Alliance
IT Architects Alliance
IT Architects Alliance
Design and Architecture of a Cloud Shopping Cart System

Preface

The main functions of a shopping cart are: 1) Similar to a traditional store, it allows users to select multiple items for checkout at once. 2) It serves as a temporary collection area. 3) For merchants, the cart is one of the best places for promotion.

Early Stage

ERP split; Business service‑oriented split; WCS split.

Shopping Cart Functional Module Overview

Layered Design

Cluster Design

From the application layer perspective, the cloud shopping cart is designed with three parts – an interaction layer, a business assembly layer, and a basic service layer (horizontal). Each part consists of one or more clusters.

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 standard shopping cart processes and non‑standard processes. Basic service layer: encapsulates data delivery from peripheral systems and core functional services.

From the application cluster perspective, two clusters are designed – a shopping‑cart cluster and a settlement‑cart cluster (vertical).

Shopping‑cart cluster: high traffic, stores sensitive user information that must not be lost (basic purchase data). Settlement‑cart cluster: handles additional checkout information, which is less sensitive (payment configuration, etc.).

Technical Architecture Design

The distributed design aims to achieve the following goals:

Stability: the system must provide 24/7 reliable service. High Performance: the core system must deliver high performance and reliable service under concurrent load. Elasticity: resources can be smoothly scaled (e.g., using VM, LXC) to handle traffic spikes. No Single Point of Failure: the system avoids any single point of failure. Fault Masking Automation: automatic fault isolation for network, application, or database failures.

Three‑Level Cache

Asynchronous Checks

Heterogeneous Storage

Advantages: simple workflow.

Disadvantages: traffic spikes and high concurrency.

Shopping Cart Payment Scheme

Heterogeneous Solution for the Payment Middle‑Platform

Nginx+LUA Aggregated Business Front‑End Interface Merging

Anti‑Scalping

Multi‑Dimensional User Feature Identification

Disclaimer: The material shared in this public account is collected from the internet, all text and images belong to the original authors, and the content represents personal views only. It is provided for learning and exchange purposes; please verify the information yourself.

Distributed SystemsSystem ArchitectureBackend DevelopmentCachingshopping cartPayment Integration
IT Architects Alliance
Written by

IT Architects Alliance

Discussion and exchange on system, internet, large‑scale distributed, high‑availability, and high‑performance architectures, as well as big data, machine learning, AI, and architecture adjustments with internet technologies. Includes real‑world large‑scale architecture case studies. Open to architects who have ideas and enjoy sharing.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.