Pods can be used to help promote important information and direct site visitors to additional information.
Easily build and integrate anything on top of the Znode eCommerce platform
The Znode eCommerce platform is in the form of a headless engine, which is made possible by the REST API. The API wraps around the main engine and core eCommerce libraries, giving you a robust and easy-to-consume layer to build and integrate nearly anything on top of the Znode eCommerce platform.
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.
The Znode Engine
The Znode engine consists of several layers and components that comprise all of the logic required to run an eCommerce platform:
Services – This layer sits just below the REST API and is responsible for invoking logic from the business libraries and aggregating data.
Business Libraries – These are the components that contain all of the primary logic for the Znode eCommerce platform.
Provider Engine – The provider engine is at the heart of the Znode platform and is a primary spot for extensibility and customization.
Search Engine – Znode comes with a very fast and powerful search engine, built using Lucene.NET, the industry standard search engine library.
Data Access – All data for Znode is stored in Microsoft’s SQL Server database and is retrieved using the .netTiers ORM, along with some custom stored procedures.
The Znode API is a completely REST-based set of endpoints that provide robust functionality for you to interact with. The REST API is a critical piece as it serves the following purposes:
- It allows you to build applications and services on top of Znode 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 for the Znode platform, 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 for working with any endpoint in the API. The caching layer is completely configurable and greatly increases overall performance and scalability of the Znode platform.
This is a promo pod