Release Date: June 20, 2020

Enhancements

[ZPD-10431] - Performance: Link Widgets

Shopper Experience

To improve the performance of the product list fetched and displayed in the link widget(s) on the PDP, a cache mechanism is implemented for WebStoreWidget/GetLinkProductList API so that the products available in the widgets can be cached. The products will then be fetched from the cache instead of the database, thereby improving the performance and reducing the loading time of the product list.
Note: The products cached for link widgets will get refreshed whenever any product is published directly or indirectly.

[ZPD-10432] - Performance: Keywords Redirect

Shopper Experience

To improve the performance of the web store search, a cache mechanism is implemented for Search/GetCatalogKeywordsRedirectList API so that the data from the Keywords Redirect can be cached. The data for the redirection URL will then be fetched from the cache instead of the database, thereby improving the performance and reducing the time required for the search to bring the results. 

Note: The cached data from Keywords Redirect will get refreshed whenever any keyword redirect is added, updated, or deleted.

[ZPD-10433] - Performance: Dynamic Styles

Shopper Experience

To improve the loading time of the styles displayed on the web store, Donut caching is implemented for Dynamic Styles so that the styles can be fetched from the cache instead of the database, thereby improving the performance and reducing the time required for the load the styles on the web-store. 

Also, a provision is made to allow Dynamic Styles to handle multiple requests simultaneously.

Important: It is recommended for custom projects to add all the new controllers/actions in RouteConfig for better performance.

[ZPD-10434] - Performance: Cart Count

Shopper Experience

The count of products available in the cart is calculated and displayed on several pages. Earlier the count always used to get fetched from the database.

With this release, the count will be saved and fetched from the session for scenarios where there is no need for a DB call. This enhancement will not only improve the performance but also the experience of customers (shoppers) visiting the web store.

[ZPD-10435] - Performance: Registering All Routes

Shopper Experience

Certain routes were identified which used to call the default route available in the route.config file. Due to which unwanted calls used to get initiated to SEO API, thereby making responses to the web store requests slower.

Therefore to improve the performance of the responses, the entries of such routes were added in the route.config file.

This enhancement has improved the performance of the web store.

[ZPD-10778] - Performance: SearchAgent.GetSeoUrlDetail Method Optimization

Shopper Experience

The SearchAgent.GetSeoUrlDetail method is optimized so that unnecessary calls to the API can be avoided when registered users log in to the web store.

This enhancement has improved the performance of the web store in cases of slug URLs.

[ZPD-10518] - Performance: JSON Minification

Shopper Experience

Earlier, API used to provide responses for properties with default or null values as well, which were not required. Due to which the size of responses used to increase, causing load on the network.

Therefore to avoid unwanted properties in response, JSON minification is introduced in Znode, which makes responses light. Also when initiating a request to the API, a Minified-Json-Response header will be set in the request and the API will return the minified JSON if this header is present in the request.

This enhancement will reduce the load on the network.
Note: Minified-Json-Response header will be set only for web-store requests

[ZPD-10582] - Performance: Donut Caching For Logged-In Users

Shopper Experience

Earlier, to improve the performance of the web store, a Donut cache mechanism was implemented for all the highly usable web pages (like the home page, product pages, category pages, etc) so that they can be served directly from the cache instead of the database.

This provision was available for guest customers (shoppers) but now will be available for logged in customers (shoppers) as well.

[ZPD-10584] - Performance: Web Store Widgets

Shopper Experience

Ajax calls are used for Home page and product detail page widgets. When these pages are loaded for the first time, all the widgets request data simultaneously, causing the slowness.

Therefore to reduce the loading time and improve the performance of the widgets, non-Ajaxified calls will be initiated in scenarios where Donut caching is enabled.

Note: Ajaxified calls will be initiated when Donut caching is disabled. 

[ZPD-10643] - Performance: Search/FullTextSearch API Optimization

Shopper Experience

Earlier, Search/FullTextSearch API used to provide slow response when configurable products were searched. This was due to an unwanted database call, which has now been removed.

This will not only enhance the performance of the search and PLP but will also reduce the loading time of the search results displayed on the search results page.

[ZPD-10711] - API Cache Durations

Shopper Experience

The cache duration of all keys is set to 60 minutes.

[ZPD-10779] - CurrentPortalCacheDuration Key Cache Duration

Shopper Experience

The duration of the CurrentPortalCacheDuration cache key is set to 20 minutes.

[ZPD-8991] - Provision To Enable Action Level Concurrent Request Handling

Shopper Experience

Znode now provides a provision to enable action level concurrent request handling. This will allow our clients to use this provision for any action(s) they want.

 

[ZPD-10842] - Performance: Published Category Details

Shopper Experience

To improve the performance of the category details, a cache mechanism is implemented for PublishCategory/GetPublishCategory API so that the category details are cached. The details will be then fetched from the cache instead of the database, thereby improving the performance and reducing the loading time of the published category details.
Note: The data cached will get refreshed whenever any category is published directly or indirectly.

[ZPD-10851] - Performance: Published Category List Details

Shopper Experience

To improve the performance of the category list details, a cache mechanism is implemented for PublishCategory/List API so that the category list details are cached. The details will then be fetched from the cache instead of the database, thereby improving the performance and reducing the loading time of the published category list details.
Note: The data cached will get refreshed whenever any category is published directly or indirectly.