manh_nguyen
Sep 4, 2024
visibility 2539
star star star star star
(4 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

Mike Malloy
Mike Malloy Sep 10, 2024 12:47 PM

No mention of it here on the Release page: https://support.optimizely.com/hc/en-us/articles/23973547163917-2024-Search-Navigation-release-notes

Looks like 16.3.0 also adds the ability to find items in the index via the editor and delete them permanently.

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |