So I'm fiddling with how you could design the basic db schema for a webshop. Sure, there's a lot of missing details here and there, but I just want to get the most basic stuff right.
Some basic requirements for the shop, which I'm trying to make a schema of:
The shop has an inventory of products. Each product has a price, but this price should vary depending on sales. Customers can make orders for multiple products at a time, and should be able to see their order history. When the order has been completed, there should be a track and trace number.
So, the following image is what I've come up with so far. I'm sure something is missing, I'm just not really sure what, also how to model the dynamic price aspect.
In an e-commerce application, the main purpose of a database is to store information for retrieving the product details, customer information, track transactions, and further, maintain the inventory. One of the biggest benefits of using a database for e-commerce is structuring vast amounts of shop data.
For example, in the Oracle Database product, a schema represents only a part of a database: the tables and other objects are owned by a single user. Note: In SQL, a view is a virtual table that is based on the result-set of a statement. A view contains both rows and columns.
Schema is of three types: Logical Schema, Physical Schema and view Schema. Logical Schema – It describes the database designed at logical level. Physical Schema – It describes the database designed at physical level. View Schema – It defines the design of the database at the view level.
As you can see, the NoSQL databases perfectly match the requirements and needs of the e-commerce market in terms of data availability and storage. Currently, the most popular database system of this type is MongoDB.
I think this is the according to your question give a flow of it how to create a schema and Additional that Link here please visit once you will find some amazing part.
A common way to handle variable price would be to introduce a rebate schema. This can be implemented as association class between Product
and Sale
by adding some rebate to amountSold. Of course there are many different ways, but this is one at hand.
Order
and Customer
.Inventory
aggregating ProductList
. To me a Inventory
lists Product
. There might be the need to a store location and a PurchasePipe
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With