The application will follow an MVC architecture. By separating the concerns between business logic, database, and front-end features, each component can be developed independently and could theoretically be changed out for a different technology at a later date.

The Repository Pattern

With the Repository pattern, we create an abstraction layer between the data access and the business logic layer of an application.

Querying: Converts LINQ-to-Entities queries to SQL query and sends them to the database.
Change Tracking: Keeps track of changes that occurred on the entities after querying from the database.
Persisting Data: Performs the Insert, Update and Delete operations to the database, based on entity states.
Caching: Provides first level caching by default. It stores the entities which have been retrieved during the life time of a context class.
Manage Relationship: Manages relationships using CSDL, MSL and SSDL in Db-First or Model-First approach, and using fluent API configurations in Code-First approach.
Object Materialization: Converts raw data from the database into entity objects.

A SQL database will store product data, user information, and order details. When a user requests a product page, it will be generated dynamically from current data in the database. Shopping cart information can be saved for as long as needed because it is saved in the database, giving the user the ability to view their cart anywhere and across devices. Administrators will have separate accounts enabling CRUD operations on the database.

Domain Model

UML Sequence Diagram