Learn about SAP Hybris and see how to configure Tomcat session management with Redis.
Let’s be friends:
Comment (0)
Join the DZone community and get the full member experience.
SAP Hybris is an e-commerce platform originally introduced in 1997. The Hybris software was acquired by the German multinational corporation SAP in 2013. In June 2018, the platform was rebranded as SAP Customer Experience in order to further integrate it under the SAP umbrella. Over the years, Hybris users have included major firms such as Adidas, Samsung, and Vodafone.
From a technical perspective, Hybris is a Java-based software application that uses a three-layer architecture including web, application, and database. It includes features such as web content management, customer service, product catalogs, and payment integrations.
In addition, SAP Hybris can be run as a cluster, which is a group of server nodes that are tightly connected and act as a single system. The benefits of using SAP Hybris clusters include high availability, parallel processing, and load balancing.
User session failover is the term for the strategies used when the server holding a user’s session fails, placing this information at risk of loss.
When a user logs into an SAP Hybris cluster, the application creates a session on one of the servers in the cluster. During times of high demand, however, the SAP Hybris load balancer may route the user to another server in the cluster that does not have the same session information. As a result, the user appears to be logged out of the application.
There are two solutions to this problem, which are often referred to as „sticky“ and „non-sticky“ sessions:
With sticky sessions, the application uses a cookie to uniquely identify users. This permits the application to always send the same user to the same server.
