Indexes and asynchronous processing
This is more of a backend thing, but in my personal opinion, even a frontend developer needs to know this part, as it does affect the website rendering process.
In Chapter 3, I’ve shared some knowledge about indexes. This is an appendix to that chapter with some more insights. As you might remember, there are two modes that indexes can run:
- On save
- Schedule
If your indexes are set to On save, the data is only updated when there are operations done on objects by the platform – for example, saving the product or selling it. There are a lot of operations that need to be run, which might affect the site speed for the customer browsing the store.
If you are using bulk import or have a third-party module that operates on SQL to update product data, you might never even see some data on the frontend. You always need to have indexes set to Schedule so that data is prepared in the background, except the Customer Grid...