10 of the best Azure AI search alternatives in 2025

## What is RAG, and why should you care?

Every day, millions of people interact with ChatGPT, Claude, and other large language models, fundamentally changing how we interact with computers. The appeal is obvious: instead of learning specific interfaces, users can simply communicate in natural language. The machine adapts to the human, not the other way around.

This shift has organizations scrambling to create similar experiences with their own data. Whether it's building a support chatbot that understands product documentation, crafting an assistant that writes personalized emails, or developing an internal tool to help employees access company knowledge, they all require the same foundation: giving LLMs access to proprietary information.

Enter Retrieval Augmented Generation (RAG), a workflow that's deceptively simple in concept:

1. User asks a question
2. The system retrieves relevant documents based on that question
3. LLM generates an answer using those retrieved documents as context

When implemented correctly, RAG provides more accurate, up-to-date responses while reducing hallucinations. But here's where most engineers go wrong: they default to vector databases without considering whether that's actually the optimal approach.

## The engineer's shortcut: Vector databases

The typical RAG implementation looks something like this:

```
User Question → Convert to Embedding → Query Vector DB → Retrieve Similar Documents → Generate Answer

```

It makes intuitive sense. Vector embeddings capture semantic meaning, so similar concepts cluster together in the vector space. By converting questions and documents to the same embedding space, you can find relevant information even when the exact keywords don't match.

Engineers love this approach because it seems elegant. You don't need complex query parsing or keyword matching – just transform everything to vectors and let similarity algorithms do the work.

But this shortcut creates two critical problems that significantly degrade the quality of the results.

## Problem 1: Unrefined queries lead to irrelevant results

The first major issue occurs at the initial step: we take the raw user query, convert it directly to an embedding, and use that to retrieve documents.

Think about what happens when you use Google. You don't always search with your actual question – you distill it to key terms that are more likely to yield relevant results. If you want to know "What's the best way to organize React components in a large project?", you might search for "React component organization best practices large applications."

LLMs excel at this kind of query refinement, but in the standard vector DB approach, we skip this crucial step. The embedding captures the semantic meaning of the original question, but that doesn't always align with the optimal search query.

## Problem 2: Vector search sacrifices precision for recall

The second problem is more fundamental: vector similarity search is strong at recall but often weaker at precision compared to traditional full-text search.

Vector search excels at finding conceptually related content (recall) - documents that discuss similar topics, even if they use different terminology. However, it's less effective at pinpointing exactly what you need (precision).

Full-text search, on the other hand, prioritizes precision. When exact keyword matches exist, they're usually highly relevant. The trade-off is that full-text search might miss conceptually similar content that uses different terminology.

This explains why many RAG systems that rely exclusively on vector databases end up implementing additional re-ranking steps after initial retrieval. It's also why vector databases increasingly add full-text capabilities – they recognize the inherent limitations of pure vector search.

## A more human approach to RAG

Since we're trying to build systems that mimic human intelligence, shouldn't we structure our RAG pipelines to mirror how humans actually search for information?

When people need to find information, they:

1. Reframe their question into effective search terms
2. Use search engines optimized for retrieving relevant information
3. Scan results to identify the most useful content

A better RAG design would follow this pattern:

```
User Question → LLM Refines Into Search Query → Hybrid Search (Combining Full-text and Semantic) → Retrieve Relevant Documents → LLM Generates Answer

```

This approach addresses both problems:

1. The LLM refines the user's original question into an optimized search query
2. Hybrid search combines the precision of full-text search with the recall of semantic search

## The solution: Simpler (and better) RAG with search engines

Here's my contrarian take: instead of jumping to vector databases for RAG, start with a quality search engine that combines full-text and semantic capabilities.

Modern search engines like Meilisearch offer hybrid search functionality that delivers better overall relevance than pure vector retrieval. They're also:

- Easier to deploy and maintain
- Optimized for fast queries at scale
- Designed with relevance as the primary objective
- More intuitive for debugging search results

For most RAG applications, the workflow becomes much simpler:

1. The user submits a question
2. LLM transforms that question into an effective search query
3. The search engine retrieves relevant documents using hybrid search
4. LLM generates a response using those documents as context

This approach aligns with how humans actually search for information, leveraging the strengths of both LLMs and search technology while avoiding unnecessary complexity.

## The power of simplicity in RAG: Back to search basics

Vector databases certainly have their place in the machine learning ecosystem, but they're not always the best foundation for RAG systems. By taking a step back and considering how humans search for information, we can build more effective, simpler RAG architectures.

The next time you're designing a RAG system, consider whether a good search engine might be the better choice. Your users (and your future self maintaining the system) will thank you.

Why you shouldn't use vector databases for RAG

Think of a digital library where finding a specific book feels like navigating a labyrinth blindfolded.

For many websites, internal search is just that—a frustrating maze. Users often get lost, give up, and leave the site. However, internal search can be a precise tool. It can guide users directly to what they need and offer insights into their behaviors and needs.

Today's internal search is more than a navigation aid. **It's a strategic asset that enhances user experience, boosts conversions, and taps into the intelligence of your data.**

## What is internal search?

Imagine a customer visiting your website to find a specific product, an employee searching your company intranet for a crucial document, or a reader looking for a blog post they remember reading last month. In each case, they probably use your site's internal search function.

### Key differences between internal and external search

Google and other search engines deliver instant, relevant results for any query, setting high expectations. However, internal search operates under different conditions.

External search engines like Google scan the entire web. They use complex algorithms and massive computing resources to rank billions of pages based on numerous factors, including backlinks, page speed, and user behavior.

**Internal search only indexes content within your digital boundaries**. These can include local files, email inboxes, specific software applications, intranets, and different cloud storage solutions.

![](https://unable-actionable-car.media.strapiapp.com/ezgif_com_video_to_gif_bce9ae142e_344cec37b7.gif "Example of customized internal seach from Hugging Face")



The main difference lies in control. Unlike Google's algorithms, you can fully control your internal search experience. This allows you to customize the search function to meet your specific content and user needs.

### Why internal search is essential

#### For websites

When visitors can't find what they're looking for on your site, they often leave. Poor search functionality is a top reason for site abandonment. Internal search acts as both a safety net and an efficiency tool.

**Internal search also generates valuable data about your visitors' intentions.** Every search query is a direct expression of user interest. This information can inform content strategy, product development, and marketing efforts. Crafting relevant keywords and phrases is crucial not only for users but also for structuring and tagging content to make it findable.

#### For SaaS

Internal search is becoming increasingly important in SaaS products to help users quickly find specific features, settings, or information within the application. As SaaS platforms grow in complexity and offer more functionalities, an effective internal search ensures users can easily navigate the system and maximize its value.

![iOS wallpaper search problem](https://unable-actionable-car.media.strapiapp.com/i_OS_wallpaper_search_problem_8067d95edc.avif "Many people are complaining about the search function in the iOS Settings app.")



Just like the complaints about the iPhone settings app's search function, a non-functioning internal search can be incredibly frustrating for users who expect to find what they need quickly and easily.

### How internal search differs across industries

The implementation and importance of internal search vary significantly based on the business model and content type.

![fuzzy search](https://unable-actionable-car.media.strapiapp.com/fuzzy_search_3f79b0e35c.avif)



**E-commerce:** For online retailers, search is often the primary navigation method for product discovery. Search accuracy is directly tied to conversion rates. Users expect advanced features like filtering by price, size, color, and other attributes. Amazon's search functionality predicts intent, [handles misspellings](https://meilisearch.org.cn/blog/fuzzy-search), and [suggests related items](https://meilisearch.org.cn/blog/personalization-recommendations).

![Search query interface social marketing](https://unable-actionable-car.media.strapiapp.com/Search_query_interface_social_marketing_453ab7d512.avif "For example, Slack lets you add filters within the search bar.")



**SaaS platforms:** Software companies need to make complex functionality discoverable. Internal search must span product interfaces, help documentation, community forums, and developer resources. Slack's search function handles conversational language across thousands of messages and respects complex permission structures.

![](https://unable-actionable-car.media.strapiapp.com/AD_4n_Xf_R_Ormjkncn9_Uj8i_Un6vaqs_Wi_I_Uln1hutwuz0h_KI_wm_GIA_P_Wry5j_Rj5_R_Altplg_VV_5_Jy_ANKPL_2_Hayt3_Jv_Ku_A_Gw9ou_P8l0va_9f26862acc_ad08c71ee1.gif)



**Content platforms:** Media sites, blogs, and knowledge bases use search to help users find relevant information quickly. Bildhistoria, a Swedish non-profit managing the country's largest collection of historical photographs, uses Meilisearch to [power discovery across their database](https://meilisearch.org.cn/blog/powering-bildhistoria-discovery) of 90,000+ images and associated metadata about people, organizations, and locations.

**Corporate intranets:** Search engines within organizations must navigate multiple disconnected systems. [**Enterprise search**](https://meilisearch.org.cn/blog/enterprise-search) **platforms provide a unified search experience** that connects to and indexes data from a wide range of internal systems, including email, cloud storage, and various business applications.

Effective internal search requires understanding both your content structure and your users' search behavior. This challenge grows with the size and complexity of your digital presence.

## Benefits of internal search for businesses and users

Internal search functions as your website's personal concierge. It guides visitors precisely where they need to go while gathering invaluable intelligence about their intentions.

### Boosting conversions through effective internal search

Search-driven visitors aren't casual browsers; they have clear intent. In fact, visitors who use search are a staggering [338% more likely](https://www.hawksearch.com/white-paper/why-do-i-need-site-search) to convert than those who don't. They're actively seeking something specific, demonstrating higher purchase intent.

When someone types "waterproof hiking boots size 10" into your search bar, they're declaring their purchase intention. **By delivering precisely matched results, you facilitate a transaction that might otherwise never happen.**

### Enhancing SEO with internal search data

Your internal search box is a valuable SEO research tool. Each query represents unfiltered customer language—the exact terms your audience uses when thinking about your products or content. This intelligence helps bridge the gap between how you describe your offerings and how customers search for them.

By tracking and analyzing these searches, you can:

- Identify content gaps
- Discover emerging trends
- Refine your external SEO strategy with authentic user language

**When you notice frequent searches for terms you haven't optimized for, you've discovered opportunities to create targeted content that meets demonstrated user needs.**

### Gaining insights into user behavior and preferences

Internal search data reveals not just what users want, but how they think. The patterns in search queries can uncover seasonal trends, regional preferences, and shifts in terminology within your industry. This behavioral intelligence extends beyond marketing—it can inform product development, content strategy, and inventory management decisions.

![Google trends search results](https://unable-actionable-car.media.strapiapp.com/Google_trends_search_results_6a871f670e.avif "You will then be able to have a dashboard like that. This one is Google Trends")



For instance, a sudden spike in searches for "sustainable packaging options" might signal an emerging customer priority that could influence your product roadmap. **These insights allow you to stay aligned with evolving customer expectations.**

### How internal search can reduce bounce rates and improve time on site

When visitors can't find what they're looking for, they often leave your site and head to a competitor. A robust internal search system acts as a safety net, catching potentially lost visitors by providing alternative paths to discovery.

By analyzing search patterns alongside user session data, you can identify which search terms lead to extended site exploration versus immediate exits. **This intelligence helps you prioritize content improvements where they'll have the greatest impact on engagement metrics that directly influence your bottom line.**

## How to implement internal search on your website

In this section, we'll explore how to select the perfect internal search solution that aligns with your platform's unique requirements and user expectations.

### Choosing the right internal search engine for your needs

Different search solutions cater to various needs. Your choice should match your specific requirements. Think of search engines as vehicles: some are fast sports cars, others are sturdy SUVs for varied terrain.

When evaluating options, consider these critical factors:

- **Scale and complexity of your content**: How much data needs indexing? Does it include multiple content types?

- **Technical resources available**: Do you have developers for complex integrations, or do you need a simpler solution?

- **Customization requirements**: Is a standard search interface enough, or do you need a customized experience?

- **Budget constraints**: Enterprise solutions offer robust features but are more expensive, while open-source alternatives like Meilisearch provide powerful capabilities at a lower cost.

Meilisearch is often an ideal choice, offering the speed and relevance of commercial solutions with the flexibility and affordability of open-source software. Its typo-tolerance and minimal configuration requirements make it appealing for teams seeking powerful search capabilities without extensive implementation effort.

<Callout intent="note">
	
	Want to dive deeper into how different search solutions compare? Check out our [comprehensive comparison of Meilisearch and Algolia](https://meilisearch.org.cn/blog/meilisearch-vs-algolia) to understand the nuances of modern search technologies.
	
	
</Callout>

### Setting up internal search tracking in Google Analytics

**Tracking search behavior is crucial** for understanding user needs and identifying content gaps. Here’s how to set up search tracking in Google Analytics 4:

- **Identify your search query parameter**: Perform a search on your site and check the URL. For instance, if the URL is `www.example.com/search?q=analytics`, "q" is your query parameter.
- **Navigate to your GA4 account settings**: Go to Admin &gt; Data Collection and Modification &gt; Data Streams, and select your web data stream.
- **Enable Enhanced Measurement** and access the settings by clicking the gear icon.
- **Activate Site Search** and click "Show advanced settings."
- **Enter your specific query parameters** if they differ from the default ones (q, s, search, query, keyword).

To analyze this data effectively, create a custom report:

- Go to the Library section in GA4.
- Choose "Create New Report" &gt; "Create detail report."
- Select "Events" as your dimension.
- Choose "Search Term" as your primary dimension.
- Add metrics like "Event Count" and "Total Users."
- Include an event filter: Event name exactly matches 'view_search_results'.

This configuration will transform raw search data into actionable intelligence. It helps you understand not just what users are searching for, but also their behavior patterns. This insight is invaluable for guiding content creation and product development. The search data you collect offers a direct glimpse into your users' needs, preferences, and challenges.

<Callout intent="tip">

Unlock advanced search potential with customizable relevancy, typo tolerance, and more. Enhance your search strategy with powerful search capabilities.
[Explore Features](https://meilisearch.org.cn/solutions/hybrid-search)

</Callout>

## Leveraging internal search data for business growth

Internal search reveals customer intent, a goldmine for forward-thinking companies. Every query highlights user needs. Optimize the search experience, then leverage that data to refine content, products, and overall strategy.

### Using search data to refine content and product offerings

Focus on high-volume/low-result queries – these pinpoint unmet needs. One content platform, spotting frequent searches for "beginner tutorials" despite having only advanced content, created a successful intro series. Search data shows *what* users want and *how* they ask for it. A monthly cross-functional "search insights review" can ensure data influences business-wide decisions.

### Identifying trends and gaps in user needs

Search data flags emerging trends. Monitor seasonal patterns to predict demand. Meilisearch offers powerful analytics, capturing subtle shifts in user language using natural language processing.

### Integrating internal search insights with marketing strategies

Use internal search insights to:

- Tailor marketing messages with **relevant keywords and promotions**
- Base campaigns on user search behavior
- Target specific user needs identified through search data

### Measuring the ROI of internal search improvements

Link search behavior to business outcomes to see real ROI.

Search users often convert 2-3x higher than non-search users, justifying search investments. E-commerce sites see higher average order values from search-initiated purchases.

### How to use internal search data to personalize user experiences

Search history: a behavioral fingerprint. Prioritize recent searches for content recommendations. Tailor navigation menus based on common searches. Strive for helpful, not intrusive, personalization. Consider context: a "lightweight jacket" search in September vs. March implies different needs.

Treat each query as customer intelligence to build responsive products, relevant content, and personalized experiences driven by user language.

## Key features of an effective internal search engine

The difference between a basic search box and a truly effective internal search system lies in its ability to understand user intent and deliver relevant results instantly. Let's explore the essential components that transform ordinary search functionality into an exceptional user experience.

### Fast and accurate search results

**Users expect near-instantaneous results—anything over 300 milliseconds feels sluggish.** But speed without accuracy creates frustration. The most effective search engines balance both, delivering relevant results at lightning speed.

Modern search platforms like Meilisearch achieve this balance through sophisticated indexing techniques. These systems prioritize both performance and relevance. They deliver results in milliseconds while maintaining high accuracy—even with typos or partial queries.

### Intuitive and user-friendly interface

The search interface should be immediately recognizable and accessible from any page. Effective implementations feature prominent placement, clear visual cues, and thoughtful placeholder text that guides users on how to search effectively.

![predictive search](https://unable-actionable-car.media.strapiapp.com/predictive_search_847ae3d9ef.gif)



[Auto-suggest](https://meilisearch.org.cn/blog/predictive-search) functionality transforms the search experience from a guessing game into a guided journey. As users type, seeing relevant suggestions not only speeds up their search process but also helps them discover options they might not have considered. **This subtle guidance can significantly improve discovery and engagement.**

### Advanced filtering and sorting options

Once results appear, users need ways to refine them based on their specific needs. [Effective filtering options](https://meilisearch.org.cn/blog/filter-scoring-guide) might include:

- Date ranges for content searches
- Price ranges for product searches
- Specific metadata fields relevant to your content type

**The key is balancing comprehensiveness with simplicity.** Offer enough filtering power without overwhelming users with too many options. Effective implementations adapt their filtering options contextually based on the search query and available results.

### AI-powered personalization and recommendations

Modern search engines incorporate machine learning to understand context and user preferences. This intelligence allows the system to personalize results based on previous interactions, location, or other relevant factors.

Recommendation engines extend this capability by suggesting related items that might interest the user based on their search behavior and the collective intelligence gathered from all site visitors.

### Access to actionable search analytics

Behind every great search implementation is a [robust analytics system](https://meilisearch.org.cn/blog/search-analytics-release). It tracks what users search for, which results they click, and where the system fails to deliver relevant results. These insights drive continuous improvement of both the search functionality and your overall content strategy.

Platforms that provide visualizations of search trends, zero-result queries, and user paths after searching give you the intelligence needed to refine your approach over time.

<Callout intent="tip">
	
	Capturing zero-result searches can highlight content gaps and unmet user needs, guiding future improvements.
	
	
</Callout>

## Enhancing digital success with internal search

Internal search serves as a strategic tool that **transforms user experience and drives business intelligence**. It connects user intent with digital content effectively.

By implementing intelligent search technologies such as Meilisearch, organizations can develop dynamic, responsive platforms. These platforms not only meet but also anticipate user needs. This shift turns the search function from a basic navigation tool into a powerful engine of engagement and insight.



Internal search: the key to better user experience and SEO  

What is full-text search and how does it work?

Federated search allows fetching information from several data sources with a single search query, which triggers an engine that seamlessly aggregates the information and outputs the key results.

This technology is helpful for enterprises that often use several databases and other storage solutions and require an internal search engine that guarantees fast and unified information retrieval.

In this piece, we will examine federated search's workings and applications in greater detail, highlighting its benefits and potential challenges.

## What is federated search?

Federated search is a search system that uses a single query to retrieve information simultaneously across multiple indices, such as databases, APIs, and cloud storage solutions.

Unlike searching on a single index, which grabs only the most accurate results for that document, federated search aggregates information from all available sources and outputs the most relevant results from the aggregated dataset.

This information retrieval mechanism is a crucial feature for SaaS applications, where users frequently need to search through all available resources regardless of type. An example you might be familiar with is searching in Slack—a single search bar to find users, messages, and shared documents.

![image1.png](https://unable-actionable-car.media.strapiapp.com/image1_14270ba4b3.png)

## What are the benefits of federated search?

Federated search brings overall efficiency in retrieving information for organizations. Some of the key benefits associated with this technology are:

* **Search across multiple sources:** With only one search bar, companies can query key information from all their data sources, including databases, Google Sheets, APIs, and cloud solutions.
* **Enhance user experience:** Since federated search requires only one widget or input to fetch all relevant data, there’s no need for multiple menus or filters to enhance the federated search results. Making the search experience and the overall interface more straightforward.
* **More relevant results:** The system matches the query against a large dataset of aggregated data sources. Therefore, the engine will look for the most relevant results across all enterprise data instead of returning lists of relevant results from separate sources.
* **Find forgotten content:** Sometimes, with such diverse data sources, the user may struggle to know precisely where they saved the meeting minutes or what folder has that great resume someone sent a few months ago. Federated search fixes this with a single search input that, with the right keywords, can fetch this information or even essential items they hadn’t initially considered. 
* **Increased productivity:** Time spent looking for the correct information in emails, databases, etc., can be drastically reduced, allowing users to concentrate on more productive tasks.

## What are the different types of federated search?

There are four different types of federated search. You should carefully choose them according to your company’s needs. 

![image2.png](https://unable-actionable-car.media.strapiapp.com/image2_08f34eb71a.png)

Now that we've quickly reviewed their pros and cons, let's explore each of these federated search types individually.
 
### Search-time merging

Search-time merging dynamically queries multiple indices in real-time, combining the results of different data sources. This approach involves maintaining a separate index instead of a unified one.

The main perk of search-time merging is that you don’t need to create a new system that aggregates all data sources into one dataset. 

In addition, you can rely on up-to-date information from constantly updated data sources. Therefore, this search type is ideal for real-time databases or live web sources.

The main drawback of this technology is its dependency on the system’s response times, which creates latency and returns outputs slower than other search types.

### Index-time merging

Index-time merging aggregates the different enterprise data sources in one centralized index before the queries occur. This architecture makes data retrieval much faster since a single source provides the results list. 

While this method is fast and does not require an index for each separate data source, it may not output the most updated enterprise information. Constant synchronization is necessary to maintain accuracy and mitigate this problem. 

This search type can be handy for companies that manage data sources that are not updated frequently and where real-time information is not a required feature.

### Federated search interface

The federated search interface is similar to the search-time merging method. Users can retrieve results from diverse systems through a unified interface instead of querying a centralized index.

This solution's front-end layer abstracts the back-end complexity and presents the results as lists indicating their source. 

This interface provides a better customer experience, allowing users to query various sources simultaneously. Advanced features, such as faceted search and relevance ranking, can also be added to the interface.

The challenges with this technology are mostly related to the complexity of creating the abstraction mechanism, and [many websites](https://meilisearch.org.cn/solutions/site-search) are not prepared to incorporate this design.

### Hybrid federated search

Hybrid federated search combines search-time and index-time merging. It uses a centralized approach, aggregating data sources in one index while querying other indices separately. 

This dual approach optimizes performance and speed by querying less frequently updated information using the centralized index while obtaining real-time data.

The system unifies the relevant outputs from the centralized and remaining sources into one final output list. Therefore, while this solution is faster than search-time merging, it can still lead to latency and slow performance.

## How does federated search work?

Here’s a breakdown of how federated search works. 

![image4.png](https://unable-actionable-car.media.strapiapp.com/image4_31706cba6b.png)

**Query submission:** The user starts by [typing terms or keywords](https://meilisearch.org.cn/blog/semantic-search) into a single search bar or interface. This interface hides the complexity of searching many sources behind the scenes.

**Routing:** Once the user enters the query, the search tool identifies which databases, APIs, cloud services, and other data sources are relevant to tackle. Once identified, the same query is sent to all these sources simultaneously.

**Query processing:** The search begins for each target index. Depending on the search type, there can be a centralized index or multiple. This choice also influences the response time and accuracy.

**Obtaining relevant results:** Depending on the search type, a single or several lists are obtained with the most relevant results across multiple data sources. 

When the architecture uses multiple lists, merging data requires more preprocessing steps. This is due to duplicate results and formatting, such as converting DateTime elements and strings to numbers. 

Also, ensuring accuracy in the final data is vital since each index sorts the relevancy depending on its information. One data source may display three results as the most relevant, while similar results are placed last on the list in another and more extensive source.

**Final output**: The system displays the final results in a single list, often with labels showing where each result came from.

Additionally, the system must be **optimized and maintained:** adding new indices or simply optimizing the capabilities requires updates and maintenance. 

In the steps involving the federated search workflow, it is key to maintain strong security measures throughout the process, apply preprocessing functions, and manage latency when some sources may take more time to deliver results.

## What are common use cases for federated search?

Federated search can serve various applications and company profiles. These are some of the most common use cases.

* **Enterprise search:** Large organizations can easily access their different data sources of information (emails, chats, CRMs, cloud storage, and databases) with a single input widget or interface. This enhances their productivity across several departments.
* **E-commerce and marketplaces**: E-commerce websites have high standards for delivering fast and accurate information. Therefore, federated search allows these companies to retrieve information in real-time from product listings, reviews, inventory data, and more, ensuring a better user experience and increasing customer satisfaction.
* **Academic and research portals:** Researchers rely on journals, institutional repositories, and databases. This technology can provide scholars with a unified research experience that accelerates knowledge discovery.
* **Healthcare and medical records:** Federated search enables instant retrieval of relevant medical information from patients, medical notes, and medical databases, enhancing diagnosis accuracy and treatment speed. It also supports compliance with privacy regulations by ensuring security and access control.
* **Government and legal systems**: Governments manage extensive records, from public policies to legal case files. Federated search makes fetching access to legal precedents, statutes, and regulatory documents easy, helping law firms, policymakers, and public agencies make informed decisions. It also enhances transparency and improves citizen access to public records.
* **Media and publishing:** Journalists and content creators do extensive research across multiple content sources, such as archives, news wires, social media, and internal databases. Therefore, they need a tool that helps them find articles, blogs, or archives faster, resulting in improved productivity.
* **Customer support and help desks:** Support teams need quick answers from knowledge bases, support tickets, and FAQs. You can consolidate these resources with federated search and decrease the response times, which improves customer satisfaction while reducing operational costs.

Depending on the application, you should carefully consider the right federated search type. For instance, e-commerce companies require real-time data, while government and legal systems may need to retrieve information quickly. Therefore, the former can leverage a hybrid system, while the latter can use a unified index approach.

## What are the challenges of federated search?

Several challenges arise during the federated search process. The main ones are:

* **Data structure:** Different indices have different data sources, such as text files, JSON, CSVs, and databases. Therefore, you must consider preprocessing steps and natural language processing (NLP) techniques to merge data from various structures and grasp their relevance.
* **Sorting and scoring results:** Indices output the relevant results using mathematical functions like cosine similarity, often used in [machine learning (ML)](https://meilisearch.org.cn/blog/neural-search). Smaller datasets may return less accurate results. When merged with more extensive data sources, extra preprocessing steps are needed to avoid noise and irrelevant results.
* **Language nuances:** International companies often have departments in different countries that use their native languages. Querying indices, primarily written in a specific dialect, must be translated into a unified language for the final results. 
* **Query robustness:** Search engines do not always recognize special characters like quotes or hyphens to refine queries.
* **Availability and timeout:** Federated search engines that offer [real-time data](https://meilisearch.org.cn/blog/vector-search) may take longer than expected to respond after the user submits the query. This can increase the bounce rate and make users less prone to revisit the website.
* **Data pipeline:** The efficiency and quality of the data pipeline are key to ensuring seamless connection of all indices and error-free application of data preprocessing steps. Therefore, these pipelines can become very robust, requiring third parties for monitoring and security.

A good team of experts is key to creating a robust federated search engine that ensures seamless connections between different sources, security, high performance, and ease of use.

## How federated search improves developer experience

Implementing federated search leads to a more streamlined search implementation process. With federated search, results are delivered in a unified list, simplifying front-end development. This goes beyond multi-index search because it comes without the added complexity of implementing front-end logic to merge, sort, and paginate the results.

In this setup, the relevance of documents can be further fine-tuned thanks to granular, per-index configuration. This allows tailoring the relevancy settings to specific data types (a specific index) rather than the entire dataset (all indices). As a federated search request comes in, the search engine can ensure that the most relevant information rises to the top.

Federated search also simplifies extending the search functionality if new types of documents need to be included. Instead of revisiting the relevancy for the entire dataset, you'll only need to focus on configuring the relevancy settings for the new document type.

## What are some examples of federated search tools?

### Meilisearch

![image7.png](https://unable-actionable-car.media.strapiapp.com/image7_a98ee81d11.png)

Source: Meilisearch

Our platform is great if you need speed and ease of use. You can submit data in different formats on the Meilisearch cloud or through an API and easily integrate [hybrid search](https://meilisearch.org.cn/solutions/hybrid-search) and other search features into your enterprise infrastructure. All of this is backed by extensive documentation and strong customer support.

**Best for:** Due to its performance and speed for data retrieval, it is best for enterprises that manage various data sources and require typo tolerance, as well as education software companies.

<Callout intent="tip">

#### Easy federated search with Meilisearch 

If you need speed and manage many data sources, Meilisearch is the best way to implement federated search.  

[Get started for free!](https://meilisearch.org.cn/cloud)

</Callout>

### Qatalog

![image6.png](https://unable-actionable-car.media.strapiapp.com/image6_37b2442a9a.png)

Source: G2

This solution can access data sources without creating indices. Some connectors are SharePoint, Google Drive, Salesforce, Zendesk, BigQuerry, and Snowflake. The indexless feature helps reduce latency and return real-time data.

**Best for:** Suitable for E-commerce websites and enterprises that require real-time data with zero or almost zero latency.

### Hyland

![image8.png](https://unable-actionable-car.media.strapiapp.com/image8_3ff93be45d.png)

Source: G2

This tool comes with several integrations and allows for creating image indices. It also introduces detectors of confidential information to protect companies from exposing it.

**Best for:** Enterprise search and healthcare companies that often rely on extensive image databases.

### Gosearch

![image10.png](https://unable-actionable-car.media.strapiapp.com/image10_ee2d4deeb0.png)

Source: G2

This tool presents an easy-to-implement unified enterprise search solution that is fast and enhanced with a generative AI chatbot. It also comes with several integrations, such as Zendesk, Slack, OneDrive, Jira, and more. 

**Best for:** IT teams and Human Resources due to its rapid implementation and chatbot integration in the search engine.

## Frequently asked questions (FAQs)

Some of the most common questions involving federated search are the following:

### How does federated search compare to unified search?

Unified search is a subtype of federated search, which uses a centralized pre-built index. It offers faster results but lacks real-time data. Other types of federated search, such as hybrid and search-time merging, use several indices, which make them slower due to the latency of some data sources, but they can deliver real-time results.

### What are the key components of a federated search system?

The federated search system requires a user-friendly interface that allows the user to input a query. The system sends this query to a single index or multiple indices. When numerous indices are involved, each uses its ranking mechanism to sort the most relevant results. The system uses a robust data pipeline to handle syntax, various languages, formats, and other data processing requirements. Finally, security is key to ensuring data protection.

### What are the drawbacks of federated search?

The system can be time-consuming to set up and requires constant optimization. Several experts are involved in creating a seamless user interface that delivers speed and performance while abstracting all the back-end steps, which include cleaning the data, applying strong security measures, and ensuring it displays the most relevant results to the user. 

### What are some open-source federated search solutions?

Some open-source federated search solutions provide a clear view of the system's backbone and allow seamless integration through their API. Meilisearch, for instance, provides extensive [documentation](https://meilisearch.org.cn/docs) in several programming languages (Java, PHP, Python, JavaScript, and more). Others, such as Milvus and OpenSearch, also open-source their code on GitHub.

## Cut through the clutter with federated search

Federated search enables performing searches against multiple indices of a search engine and returns a single, consolidated list of results. With a search engine that supports federated search, developers can build more relevant user search experiences without incurring additional complexity.

Overall, this tool boosts productivity and reduces costs across several divisions inside a company while enhancing customer support and user experience.

Federated search is available in Meilisearch 1.10 and higher. The documentation explains how to implement federated search with Meilisearch. 

What is federated search: Complete guide [2025]

AI-powered search: What you need to know [2025]

The 10 best AI enterprise search tools and platforms [2025]

We're excited to announce the release of Meilisearch v1.14.  In this article, we'll highlight the key changes and improvements in this release.

For a complete list of all updates and fixes, please visit the [changelog](https://github.com/meilisearch/meilisearch/releases/tag/v1.14.0) on GitHub.


<Callout intent="tip">

These powerful new features are coming soon to [Meilisearch Cloud](https://cloud.meilisearch.com/#release-v1-14&utm_source=blog). Sign up now to be among the first to experience the latest improvements!

</Callout>


## New: granular filterable attributes settings

With Meilisearch v1.14, you can configure filterable attributes using an [advanced object format](https://meilisearch.org.cn/docs/reference/api/settings#filterable-attribute-object) that lets you specify exactly which filtering features to enable for each attribute pattern:

```json
{
	"filterableAttributes": [
	  {
	    "attributePatterns": ["genre", "artist"], 
	    "features": { "facetSearch": true, "filter": {"equality": true, "comparison": false } }
	  },
	  {
	    "attributePatterns": ["*rank"],
	    "features": { "facetSearch": false, "filter": {"equality": true, "comparison": true } }
	  },
	  {
	    "attributePatterns": ["albumId"],
	    "features": { "facetSearch": false, "filter": {"equality": true, "comparison": false } }
	  },
	]
}
```

* **String attributes** (e.g., `genre`, `artist`): enable facet search and equality operators (`=` / `!=`) for categorical filtering, while disabling comparison operators (`>`, `<`, `>=`, `<=`), which are unnecessary for string values.
* **Numeric attributes** (e.g., `*rank`): enable comparison operators (`>`, `<`, `>=`, `<=`) for range filtering, while disabling facet search, as it's not relevant for numerical data.
* **Unique identifiers** (e.g., `albumId`): enable equality operators for exact matching, while disabling unused features such as comparison operators and facet search.

This targeted configuration can notably boost indexing performance. 

## Experimental: composite embedders

Meilisearch 1.14 introduces a new experimental feature that lets you use [different embedders at search and indexing time](https://meilisearch.org.cn/docs/reference/api/settings#indexingembedder-and-searchembedder), allowing you to optimize for both throughput and latency.
* Use a remote embedder for indexing in bulk, as remote embedders provide the highest bandwidth (embeddings/s)
* Use a local embedder for answering search queries, as local embedders provide the lowest latency (time to first embedding)

Configure your embedders using the new `composite` [source type](https://meilisearch.org.cn/docs/reference/api/settings#source). For instance, you can combine a local Hugging Face model for fast search with a remote inference endpoint for efficient indexing:

```json
{
    "embedders": {
        "text": {
            "source": "composite",
            "searchEmbedder": {
                "source": "huggingFace", // locally computed embeddings using a model from the Hugging Face Hub
                "model": "baai/bge-base-en-v1.5",
                "revision": "a5beb1e3e68b9ab74eb54cfd186867f64f240e1a"
            },
            "indexingEmbedder": {
                "source": "rest", // remotely computed embeddings using Hugging Face inference endpoints
                "url": "https://URL.endpoints.huggingface.cloud",
                "apiKey": "hf_XXXXXXX",
                "documentTemplate": "Your {{doc.template}}",
                "request": {
                    "inputs": [
                        "{{text}}",
                        "{{..}}"
                    ]
                },
                "response": [
                    "{{embedding}}",
                    "{{..}}"
                ]
            }
        }
    }
}
```

Meilisearch automatically selects the appropriate embedder based on the current operation.

Activate this feature in your project overview by checking the "Composite embedders" box under "Experimental features". If you are self-hosting Meilisearch, [enable it](https://meilisearch.org.cn/docs/reference/api/experimental_features) via the `/experimental-features` route. 

## Experimental: cache embeddings

Meilisearch 1.14 brings a new experimental feature that allows you to [cache search query embeddings](https://meilisearch.org.cn/docs/learn/self_hosted/configure_meilisearch_at_launch#search-query-embedding-cache), significantly improving performance when the same query is run multiple times.

To enable the search query embedding cache, launch Meilisearch with either instance option specifying the maximum number of entries to store in the cache:
* the `--experimental-embedding-cache-entries=150` flag
* the `MEILI_EXPERIMENTAL_EMBEDDING_CACHE_ENTRIES=150` environment variable

When enabled, Meilisearch stores the embedding vectors for search queries, eliminating the need to repeatedly generate embeddings for identical queries. This is particularly valuable in scenarios where:

* The same queries are frequently repeated
* You're using multi-search across multiple indexes
* You've implemented local sharding where identical queries are sent to different indexes

## New: get documents by id

You can now [get a set of documents by their primary keys](https://meilisearch.org.cn/docs/reference/api/documents#get-documents-with-post):

```json
// POST /indexes/INDEX_UID/documents/fetch
{
    "ids": [785084, 44214, 473],
}
```

The above query will return the corresponding documents:

```json
{
    "results": [
        {
            "id": 44214,
            "title": "Black Swan"
        },
        {
            "id": 473,
            "title": "Pi"
        },
        {
            "id": 785084,
            "title": "The Whale"
        }
    ],
    "offset": 0,
    "limit": 20,
    "total": 3
}
```

## Contributors shout-out

We want to give a massive thank you to the contributors who made this release possible. Special thanks to [@MichaScant](https://github.com/MichaScant) for their work on [Meilisearch](https://github.com/meilisearch/meilisearch), [@oXtxNt9U](https://github.com/oXtxNt9U) for contributions to [Heed](https://github.com/meilisearch/heed), [@ptondereau](https://github.com/ptondereau) for efforts on [Arroy](https://github.com/meilisearch/arroy), and both [@NarHakobyan](https://github.com/NarHakobyan) and [@mosuka](https://github.com/mosuka) for their contributions to [Charabia](https://github.com/meilisearch/charabia). We’re deeply grateful for your support and collaboration.

---

And that’s a wrap for v1.14! These release notes only highlight the most significant updates. For an exhaustive listing, read the [changelog](https://github.com/meilisearch/meilisearch/releases/tag/v1.14.0) on GitHub.

---

For more information, subscribe to our [monthly newsletter](https://dub.sh/meili-newsletter#release-v1-14&utm_source=blog), or join our [Product Discussions](https://github.com/orgs/meilisearch/discussions).

For anything else, join our developers community on [Discord](https://discord.meilisearch.com/#release-v1-14&utm_source=blog).

Meilisearch 最新消息与公司动态

2025 年十佳 Azure AI 搜索替代方案

为什么不应该将向量数据库用于 RAG

站内搜索：提升用户体验和 SEO 的关键

什么是全文搜索以及它是如何工作的？

什么是联邦搜索：完整指南 [2025]

AI 驱动的搜索：您需要了解的一切 [2025]

2025 年十佳 AI 企业搜索工具和平台

Meilisearch 1.14

2025 年十佳 Elasticsearch 替代方案和竞争产品