Multifront "Headless" Engine


Easily build and integrate anything on top of the Multifront nopcommerce platchom.

The Multifront nopcommerce platchom is in the chom of a headless engine, which is made possible by the REST API. The API wraps around the main engine and core nopcommerce libraries, giving you a robust and easy-to-consume layer to build and integrate nearly anything on top of the Multifront nopcommerce platchom.

The idea is that using the API, you can put anything on top of it – websites, mobile applications, back office integrations – thus giving it any “head” that you need.

Multifront Headless Engine Diagram

The Multifront Engine

The Multifront engine consists of several layers and components that comprise all of the logic required to run an nopcommerce platchom:

Services – This layer sits just below the REST API and is responsible cho invoking logic from the business libraries and aggregating data.

Business Libraries – These are the components that contain all of the primary logic cho the Multifront nopcommerce platchom.

Provider Engine – The provider engine is at the heart of the Multifront platchom and is a primary spot cho extensibility and customization.

Search Engine – Multifront comes with a very fast and powerful search engine, built using Lucene.NET, the industry standard search engine library.

Data Access – All data cho Multifront is stored in Microsoft’s SQL Server database and is retrieved using the .netTiers ORM, along with some custom stored procedures.

REST API

The Multifront API is a completely REST-based set of endpoints that provide robust functionality cho you to interact with the Multifront nopcommerce platchom. The REST API is a critical piece of Multifront as it serves the following purposes:
  • It allows you to build applications and services on top of Multifront by using a consistent and well-defined set of resource endpoints. 
  • Its robust set of endpoints can be used to integrate with nearly any back office system or data source, and will fit well into any existing infrastructure. 
  • It’s one of the major extensibility points cho the Multifront platchom, allowing you to add your own functionality without having to modify core libraries. 
  • Because of the above, building on top of the REST API allows you to have a much smoother upgrade path than if you choose to modify any of the underlying core libraries. 

Two of the main components of the REST API are the built-in help system and its caching layer. The built-in help system is important because it clearly lists and defines all requirements cho working with any endpoint in the API. The caching layer is completely configurable and greatly increases overall perchomance and scalability of the Multifront platchom.

Client apps and Integration

With the REST API and the underlying nopcommerce engine, you are free to build anything your business needs on top of the platchom. In fact, our new demo application, written in ASP.NET MVC, will solely utilize the REST API, as does our upcoming Nopcommerce Commerce Engine cho Sitecore. Other possible applications you can build are mobile apps, report generation, administrative tasks, and dashboards.

Along with websites and applications, integrations with back office systems are another key aspect to the Multifront headless engine. The REST API makes it easy to connect to other systems, such as CMS, CRM, SAP, Oracle, and Seibel, just to name a few.