Azure-docs: Question on the Azure Search .Net SDK latency

Created on 17 Apr 2018 · 3Comments · Source: MicrosoftDocs/azure-docs

Hi,
It is probably a stupid question but I wonder if using Azure Search with the .Net SDK is not going to create an extra latency as we channel requests from the client to the web app controller which in turn will call the azure search engine, whereas the most straightforward will be to call the azure search instance directly from Javascript. Is that a correct reasoning?

Thanks

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 62162979-3bcf-4557-a11a-b74d7b121581
Version Independent ID: d6560736-a54c-c3e2-9333-83936c066360
Content: How to use Azure Search from a .NET Application
Content Source: articles/search/search-howto-dotnet-sdk.md
Service: search
GitHub Login: @brjohnstmsft
Microsoft Alias: brjohnst

cxp in-progress product-question searcsvc triaged

Source

Ponant

All 3 comments

@Ponant Thanks for the feedback! We are currently investigating and will update you shortly.

BryanTrach-MSFT on 17 Apr 2018

@Ponant Yes, there will be more latency if you have a web app between your client and your search service. However, we still recommend this architecture in most cases because otherwise you could be putting api-keys at risk by exposing them to the client. What we recommend is that you call your search service directly from JavaScript running in the browser only if you're fine with your data being publicly disclosed and your browser-based client uses a query api-key (definitely not an admin api-key).

brjohnstmsft on 20 Apr 2018

👍1

@brjohnstmsft Thank you for the reply.

@Ponant We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and tag me in your reply. We will gladly continue the discussion.

BryanTrach-MSFT on 21 Apr 2018

👍1

Was this page helpful?

0 / 5 - 0 ratings