Everything else is optional
Posted: Mon Jan 20, 2025 3:21 am
Until you receive the first results for your filter, or rather until you evaluate the speed of receiving. Disappointment also awaits you when you will be tinkering back the capacious and convenient structure that Elastic returned to you in Bitrix, but there is nothing to be done about it in fact, there is nothing to be done vue and template reworking will help us, but that is a completely different story. If we put aside prose, the algorithm for implementing elastic into any site structure on Bitrix will contain the following main steps Collecting information for the index Implementation of.
API for generating requests main ones Replacing the data output belgium telegram data you can develop as powerful an integration system as you like, but the general scheme will be exactly this. But there is a nuance... All this is really great, elastic is a powerful engine that covers most of our requests. Based on my experience of integrations, I can note the following advantages Reducing the load on the site Improving page loading speed More accurate search results that take into account typos, errors, and language capabilities Data exchange is much faster than creating a faceted index..
Data is stored in a format convenient for development But sometimes all these advantages fade from one point, which is often not included in the integration with Elastic everything else remains on Bitrix. Yes, of course, the speed still increases, but take this advice refuse the standard implementation of the filter component. The speed with which it forms an array for filtering, to put it mildly, leaves much to be desired. In my practice, real results of page acceleration by several times were achieved only when reworking the catalog and filter components on Vue a highly loaded online store literally.
API for generating requests main ones Replacing the data output belgium telegram data you can develop as powerful an integration system as you like, but the general scheme will be exactly this. But there is a nuance... All this is really great, elastic is a powerful engine that covers most of our requests. Based on my experience of integrations, I can note the following advantages Reducing the load on the site Improving page loading speed More accurate search results that take into account typos, errors, and language capabilities Data exchange is much faster than creating a faceted index..
Data is stored in a format convenient for development But sometimes all these advantages fade from one point, which is often not included in the integration with Elastic everything else remains on Bitrix. Yes, of course, the speed still increases, but take this advice refuse the standard implementation of the filter component. The speed with which it forms an array for filtering, to put it mildly, leaves much to be desired. In my practice, real results of page acceleration by several times were achieved only when reworking the catalog and filter components on Vue a highly loaded online store literally.