Caching is not mandatory. However, it is strongly recommended that your organization implement cachine for commercial and enterprise high scalability applications.
The deployment architecture has been discussed at length in the deployment options. The IL has been designed to allow configuration for the BS artifact around identity management, startup package and caching. The only drawback for implementing caching in the IL layer is the requirement that the package be released. i.e. beta and open packages will not be cached due to how the packagemanager is implemented. This issue however can be partially resolved by adding caching to the importpkgs
at the application root level, assuming that the subsequent package loads are done by importpkgs
.
Also remember that import_pkgs
method can not solve the initial loading of the root application. The only solution is to use provide the caching to the IL layer.
Use the X-IZYCIRCUS-RENDER-CACHE-MISSES
HTTP header to get a list of packages that need to be released
:
X-IZYCIRCUS-RENDER-CACHE-MISSES:mainloader,izyware,frame/companyportal1,marketing/sem,marketing/social,izyware/viewer/catalog,pulse/catalogbuilder
X-IZYCIRCUS-RENDER-TIME-MS:2484 X-IZYCIRCUS-RENDER-CACHE-MISSES:izyware,frame/companyportal1,marketing/sem,marketing/social,izyware/viewer/catalog,pulse/catalogbuilderX-IZYCIRCUS-RENDER-TIME-MS:2681
X-IZYCIRCUS-RENDER-CACHE-MISSES:frame/companyportal1,marketing/sem,marketing/social,izyware/viewer/catalog
X-IZYCIRCUS-RENDER-TIME-MS:2161 X-IZYCIRCUS-RENDER-CACHE-MISSES:marketing/social,izyware/viewer/catalog,pulse/catalogbuilderX-IZYCIRCUS-RENDER-TIME-MS:1665
X-IZYCIRCUS-RENDER-CACHE-MISSES:
X-IZYCIRCUS-RENDER-TIME-MS:1645deployment options: https://izyware.com/