|
|
|
|
|
by dclara
4499 days ago
|
|
It's interesting that you are talking about "two-tiered search would decentralize efforts to improve algorithms". But you mentioned that "this solution does not need to be distributed: sites can share their local indexes and ranking algorithms with the routing search engine." Can you elaborate a little bit about why it's not a distributed solution if sites share their local indexes with the routing search engine? |
|
Yes, sure. I use the concept of distribution in the sense of separating a process within different entities (search router and local searches).
In the distributed case the "search router" queries other sites to determine the best results. For example, searching for code samples involved querying Stack Overflow, Code Project, Forums, etc. This approach is clearly expensive: you rely on the other sites speed, web service availability, etc.
The non distributed approach is just receiving their algorithms and data and processing everything in the router search engine. Obviously this solution can be implemented in a distributed way inside the search engine but it is not distributed in the sense of distributing the process within different entities.
In the two cases you are distributing efforts, one of the key goals of this approach because it is really difficult to compete with Google. Google "knows" how to give good results in diverse areas while in the proposed attack vector you rely on others for part of this optimization. A movie site should know how to give good results about movies while a site related to books knows about books.
It's important to note that the vast majority of search results ends in relatively few sites, so if the top visited sites implement this approach Google search market share can be challenged. Obviously we don't really know if this approach will work in practice until we see it.