In SAP Commerce, frontend applications often retrieve the latest data by periodically requesting updates from the server. For instance, this could involve checking for new notifications every few seconds or refreshing a page every 30 seconds to display the most recent content. While straightforward to implement, this approach has notable drawbacks, including increased server load, unnecessary network traffic, and a suboptimal user experience due to update delays.
SAP Commerce automatically creates Swagger documentation for all endpoints, including both OOTB and custom ones, as well as those from OOTB extensions like “b2bocc”. The extensive number of OOTB endpoints can lead to a crowded Swagger interface, making it hard to navigate and find particular endpoint.
Changing log level and properties from HAC is often used by developers for various support things. Unfortunately on SAP Commerce Cloud (CCv2) there is no more such possibility, as HAC is not available on storefront nodes.
In article SameSite cookie issue in Hybris is described, how to fix issue with SameSite cookie attribute. But, unfortunately, it is not working with enabled session persistence.
Modern web development tend to use fronted frameworks with API rest calls to hybris backend. Such approach skips hybris CMS caching system and can lead to performance issues. One of the possible improvement would be to utilize caching on browser side and in such way decrease amount of requests send to server by browser.