Lazy loading
Loading resources when the intended user step needs them rather than immediately.
What is lazy loading?
Lazy loading defers loading a resource until a later need, such as opening a view or approaching an image. It can apply to code, images or other content. Code splitting creates separate pieces of code; lazy loading determines their deferred loading. The terms therefore do not mean the same thing. Actual effects depend on content, connection and use.
In a fictional portal, a document preview loads only when opened. Customers see a loading notice meanwhile; on failure they can respond appropriately or retry. The team checks whether deferral supports the workflow. Resources important to the first view should not all be deferred indiscriminately. Less data loaded initially does not guarantee a shorter wait on later opening or replace checking the intended journey.
Sources
Related terms
- Code splittingDividing program code into separately loadable parts and planning when they load.
- BundlerA tool that groups connected modules and resources into files for delivery.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
- Cache invalidationCache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps