• Post Reply Bookmark Topic Watch Topic
  • New Topic

Typical Architecture/Flow for an ecommerce application  RSS feed

 
Mike Anna
Ranch Hand
Posts: 117
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear All,

I am (rather, will be) trying to build a shopping cart as a return of good will for a friend of mine.

I am however still dabbling with what kind of architecture/flow that I should be following. Following are the typical to-do that I have been able to think of.

1) 3 sides to it. a) display b) administering the site c) Database

The administering console will list all the products available in the DB and the administrator will be able to select the products he wishes to offer promotions on. The admin will be able to make a) special offers b) Combined offers c) Discounts

2) The Servlet would have to be coded such that it picks up the changes forced by the admin console.

3) Would require to categorise the items that need to be stored in the db.

I have no clue how I would start off.

I would be grateful if someone can add or subtract from this also I would appreciate if some one could point me to a direction.
 
Bryce Martin
Ranch Hand
Posts: 269
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You need to start by designing your DB. Once you know how you want to store and relate all your data you can write a nice user interface to work with it. You need to create your inventory tables, your customer tables, and any other tables you need to create. Make a long list of all the information you will want to have and then figure out how you want it to be structured and related.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!