What does the proxy / api do? #1273
-
The docs say is recommended to use a proxy in production and the examples refer to |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Hey there! Sorry for late reply. Rather than all the work of transforming ui search requests (query, filters, sorting) into elasticsearch queries and performing network requests to elasticsearch done in the browser, all of this can be done in node. When configured in this way using searchkit/api, Searchkit instantsearch client will forward the ui search requests to your api server instead. this is great for those who don’t want to expose their elasticsearch host publicly and provide a layer in between the browser and server with performance monitoring, connection throttling. |
Beta Was this translation helpful? Give feedback.
-
The difference between the link you shared and searchkit/api is that whilst elasticsearch is read only, you can still perform any query you want to elasticsearch, potentially raising DOS attacks with crafting expensive queries. Searchkit api hides elasticsearch and provides an api built for search use-cases. The elasticsearch queries are generated on the node api rather than on the browser. |
Beta Was this translation helpful? Give feedback.
-
So when Searchkit communicates directly with Elasticsearch it produces JQL queries? When Performance monitoring, connection throttling, etc could be configured but |
Beta Was this translation helpful? Give feedback.
The difference between the link you shared and searchkit/api is that whilst elasticsearch is read only, you can still perform any query you want to elasticsearch, potentially raising DOS attacks with crafting expensive queries.
Searchkit api hides elasticsearch and provides an api built for search use-cases. The elasticsearch queries are generated on the node api rather than on the browser.