Platform Cache service
Hi Experts, this may seem like a silly question, but we recently upgraded from v7.X of the portal to v8.4, and notice a new Platform Cache service has been installed. We've also noticed many "Cireson.Core" tables have been added to the ServiceManagement database.
We tried to find relevant documentation on the Cireson support portal -- but couldn't find anything. Can anyone enlighten us on what this new service is doing, etc. ?
Thanks!
Answers
What is the functionality difference between Cache Builder service and Platform Cache?
Also, can this service be disabled on portal that does not run Asset Management?
It seems, this service was planned to improve some portal features. This is the excerpts from other community comment related to Platform Cache posted September 2016. https://community.cireson.com/discussion/comment/4829#Comment_4829
:"...the Cireson Platform cache into the Cireson Portal which will allow us to do many things with respect to caching WI, CI, develop add-ons, etc..."
So, can someone give complete information related to this service. Should this service be activated in normal environment or can be disabled? What about Servers in NLB environment? Does one server or both need to run this mysterious service?
Thank you
This service is the newer caching technology from Cireson. CacheBuilder is the older one. In the latest release, only Asset Management items are cached by the Platform Cache service but in time, more a more items could be cached using this technology. The Service does two things (1) the caching of the data and (2) serves the API endpoints for the cached data. These endpoints support oData format making them more efficient and versatile than the CacheBuilder endpoints which is great.
In a multi Portal environment, (again unlike the CacheBuilder) you will need this service to be running on ALL servers. This is because they serve the API endpoints - so which ever server you are connected to via a NLB needs to be able to do this - and because they are more intelligent than the CacheBuilder and won't cause problems by running in multiple places.
Does this help?
Geoff