Commerce Core overview
The following table describes the concepts of Commerce Core:
Concept |
Description |
---|---|
Activity |
An internal construct that wraps a specific set of work for activity tracking, for example, for reporting and performance. The solution implements this as a A An example of an activity is to monitor performance of an action against an SLA and report actions outside the SLA, or to generate an alert. |
Approval |
Basic approval commands and pipelines to facilitate a basic approval process. Approvals are used by pricing and promotions to seek the approval of changes before implementing. |
Authentication |
The ability to authenticate a call to the service API using certificates. |
Bootstrap |
Commands and pipelines to support bootstrapping the solution. The |
Caching |
Commands and pipelines to support in-memory caching. This provides the ability to have environment-specific caching, to specify cache priorities, and to clear the cache. Caching functionality, in turn, leverages the |
Command |
Basic structure for supporting the concept of commands. A command acts like the API in a task-driven API. |
Component |
Basic structure for supporting compositional extensibility, including the component class and various base components. |
Context |
A call-level context called |
Controller |
Basic controllers that make core functionality available through the Service API. |
Converter |
Custom JSON converters for the Service API. |
Entity |
Commands, policies, and pipelines to support reading and writing commerce entities. A |
Environment |
Commerce environments provide the ability to have separately configurable pools of data and service functionality that run together in a single-service instance. Environments can share the same persistent store as other environments or be separated into their own exclusive persistent store. |
Event |
Basic infrastructure to support events and event-driven actions. |
Exception |
Basic |
Globalization |
Commands and their pipelines to support globalization, including support for multicurrency and localization. |
List |
Commands and pipelines to support basic list functionality, including basic list management. Use |
Location |
Commands and pipelines to support locations, for example, retrieving supported countries and country information. |
Logging |
Support for core logging using SeriLog and to specify logging using Microsoft Application Insights. |
Media |
Core classes to support media types and policies, including a |
Minion |
Commands and pipelines to support minions including the |
Model |
Basic core models, which are POCO classes that are reusable inside entities and components. Models can be used to present data as part of a command response, in the models collection. Models are listed in the |
Node |
A node is a running instance of the Service API. Core pipelines, blocks, and policies that enable basic node functionality. |
Performance |
Commands and policies to support tracking and integrating with performance counters for commands. |
Pipeline |
Core commands and models to support pipeline functionality. Pipelines, in turn, leverage the |
Plugin |
Core support for the Commerce pluggable extensibility. |
Policy |
A named, versionable and variable set of data that can be used as facts within behaviors to influence behavioral outcomes. This provides an auditable mechanism for viewing, simulating, and changing core decision criteria that might be used by business processes or other policy-driven behavior. Various plugins have specialized policies to add additional facts to existing policies and/or new policies, or to implement new concepts, such as dynamic pricing. Policy characteristics include:
Policies are listed in the |
Provider |
Core interfaces for an |
ServiceApi |
Core models and policies to enable the basic Service API. |
Transaction |
Core functionality to support transactionality in the solution. |