Opticon Stockholm is on Tuesday September 10th, hope to see you there!

Manh Nguyen
Sep 4, 2024
  166
(3 votes)

Non-blocking Search with Optimizely Search & Navigation

We are thrilled to announce the integration of asynchronous functions into Optimizely’s Search & Navigation features, which have been supported since version 16.3.0. By using these functions, you can leverage the benefits of asynchronous programming and performance improvements. They are particularly helpful if you are building your app with a microservices architecture or simultaneous searching for better user experiences.

The current synchronous functions such as search features, tracking, indexing...can be marked as deprecate in the future.

We've already known the advantages of Asynchronous programming:

  1. Enhanced Performance: Asynchronous operations enable non-blocking processes, reducing wait times and improving overall system responsiveness.
  2. Scalability: Handle multiple requests simultaneously, ensuring consistent performance even during peak usage.
  3. User Experience: Faster response times lead to a smoother, more dynamic user experience.

How we leverage these advantages in Search & Navigation?

Imagine an user searching for a product on your e-commerce site. With asynchronous search, the request is processed instantly. Simultaneously, tracking and statistics operations run in the background, updating user interactions in real-time without impacting the search performance. Paging through results remains smooth and quick, giving users a better experience.

var results = await SearchClient.Instance
.UnifiedSearch()
.For("search navigation")
.WithAndAsDefaultOperator()
.UsingAutoBoost()
.ApplyBestBets()
.Track() // statistical track will run asynchnorously and not affect to the search request
.GetResultAsync();

By integrating asynchronous functions, Optimizely Search & Navigation ensures your platform is future-proof, delivering better performance and a better user experience. Upgrade today to experience the difference!

See developer's document for more detail and please don't hesitate contact us if you have any question or feedback.

Sep 04, 2024

Comments

Please login to comment.
Latest blogs
Handling Nynorsk and Bokmål in Optimizely CMS

Warning: Blog post about Norwegian language handling (but might be applicable to other languages and/or use cases). Optimizely have flexible and...

Haakon Peder Haugsten | Sep 5, 2024

Remove Unwanted properties for Headless Implementation using Content Delivery API

While working with Headless, whenever we want to send data to the front end, many properties are also shown in JSON that we don't wish to, which...

PuneetGarg | Sep 4, 2024

Optimizely Headless Form Setup

1. Create empty CMS applications First, let’s setup an empty CMS application. Install the NuGet packages in your solution using the NuGet Package...

Linh Hoang | Sep 4, 2024

Default caching on search request on Search & Navigation

For the better performance, Search & Navigation .Net client has provided StaticallyCacheFor method for caching your search result in a specific of...

Manh Nguyen | Sep 4, 2024

Working with Translations in Optimizely

Ensuring that content is accessible and comprehensible in multiple languages is essential for any global business. Optimizely, combined with Langua...

Luc Gosso (MVP) | Sep 1, 2024 | Syndicated blog