You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing the plugin I came to the following conclusion...
after an update in Kentico Kontent the Gatsby build is triggered.
Graphql loads all available content from Kentico Kontent.
Gatsby performs a search to retrieve the matchFields of all available content in Algolia.
Gatsby does local matching to see what nodes needs to be updated/deleted/created based on comparing both arrays.
My question... concerns.... Does this scale when you have a real high number of content?
Or am I missing something in my current implementation / insights?
Kind regards
The text was updated successfully, but these errors were encountered:
No, when the objects would no longer fit in memory, that could be an issue, in which case it can be more interesting to sync the Algolia index directly to algolia without involving the Gatsby plugin
Hi
When testing the plugin I came to the following conclusion...
My question... concerns.... Does this scale when you have a real high number of content?
Or am I missing something in my current implementation / insights?
Kind regards
The text was updated successfully, but these errors were encountered: