Database design for Taobao and JD.com’s multi-specification combination products

JD.com and Taobao have different approaches to combining products with multiple specifications.

• JD.com treats each combination as a product, so the same product has many specifications, that is, many products.

• On Taobao, there is only one product. Click on different specifications to see different prices.

The development language is PHP and the database is mysql. Requirements: Merchants can customize specifications and there is no limit to the number of specifications and specifications.
Which of these two methods is better? Which one is easier? How should its databases be designed?

Reply content:

JD.com and Taobao have different methods for combining products with multiple specifications.

• JD.com treats each combination as a product, so the same product has many specifications, that is, many products.

• On Taobao, there is only one product. Click on different specifications to see different prices.

The development language is PHP and the database is mysql. Requirements: Merchants can customize specifications and there is no limit to the number of specifications and specifications.
Which of these two methods is better? Which one is easier? How should its databases be designed?

Hope this article can help you, http://www.cnblogs.com/mmmjiang13/archive/2012/07/05/2575538.html

Our company uses a single product model, I don’t know which one is better, each has its own advantages...
Personally, I think a single product is simpler...
Simple design description:
Single product: product-product type-specification-specification (combination)&price
Multi-product 1: Parent product - child product... // Infinitus classification table
2: Parent product category - child product

The above is the content of the database design of Taobao and JD.com's multi-specification combination products. Please pay attention to more related content PHP Chinese website (www.php.cn)!