Podcast
Questions and Answers
Which of the following components is NOT part of the Configured Commerce development architecture?
Which of the following components is NOT part of the Configured Commerce development architecture?
What is the primary role of the Configured Commerce.Web project?
What is the primary role of the Configured Commerce.Web project?
In which version of Configured Commerce were the core commerce models split into self-contained modules?
In which version of Configured Commerce were the core commerce models split into self-contained modules?
Which component is responsible for handling the Unit of Work and Repository patterns in the Configured Commerce architecture?
Which component is responsible for handling the Unit of Work and Repository patterns in the Configured Commerce architecture?
Signup and view all the answers
Which of the following elements is likely part of the Configured Commerce presentation layer?
Which of the following elements is likely part of the Configured Commerce presentation layer?
Signup and view all the answers
Study Notes
Configured Commerce Development Architecture
-
Configured Commerce is built using various components, including widgets, modules, handlers, services, directives, controllers, and more.
-
The development architecture is organized into three core libraries: Configured Commerce.Web, Insite.Module, and Insite.Model.
Configured Commerce.Web
- This library is an ASP.NET MVC application.
- It is responsible for client-side models and services that connect to the WebAPI layer in Optimizely modules.
- It houses widget views, AngularJS directives, controllers, and services.
Insite Module
- In earlier versions (Configured Commerce 3.7 and older), all models and the persistence layer were housed in the "Insite.Model" library.
- Starting with version 4.0, core commerce models were separated into self-contained modules.
- Examples of these modules include: Insite.Account, Insite.Cart, Insite.Catalog, Insite.Customers, Insite.Order, and Insite.Requisition.
- While these modules are mostly self-contained, they rely on the presentation layer of each corresponding component, which is located in the "Configured Commerce.Web" project.
Insite.Model
- This library manages the Unit of Work, Repository, Domain Services, ContextProvider, and platform persistence.
CMS Front-End Architecture
- There are two main types of CMS architectures: Classic CMS and Spire CMS.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
Dive into the intricacies of Configured Commerce development architecture, exploring its core libraries and components. Understand how the Configured Commerce.Web library interacts with ASP.NET MVC and the significance of the Insite Module in version updates. This quiz will test your knowledge of each component's role within the architecture.