Monthly Archives: June 2016

Hybris + SolrCloud: sharding and distributed indexing

The traditional Hybris Solr cluster has a number of drawbacks, including a lack of failover and scaling capabilities. In this post, I explore SolrCloud as one of the possible options for resolving these issues.

SOLR-based dynamic availability groups. PoC: 500K availability groups

Situation I am still working on overcoming hybris’ limitations. Today’s topic is about personalized catalogs. In one of the previous blog posts, I talked about personalized prices for 500,000 customer groups. This time I want to tell you about personalized product availability. It is clear that in most cases the number of availability groups is […]

90M unique prices for 500K user groups

Situation Today’s challenge is about comprehensive pricing. 500,000 customers have unique prices for 180 products. In total, 90,000,000 priced items are in the system. Having logged, the customers should see their personal price. This is an extreme case of customer group prices. Complexity For the small number of  customer groups, the solution seems trivial. Indexed products […]

Visual representation of hybris data model (items.xml)

Features: Processing all/selected hybris Types of the all/selected hybris Extensions Detailization control: some/all attributes on/off Enabling/disabling showing many-to-many relations Architecture: implemented as regular hybris addon (localextension.xml). No Update is required. Generates graphviz script (“dot” language, digraph). The extension uses Graphviz to convert the diagram into PNG. Graphviz is not required, but highly recommended. In case […]

hybris/OKTA SSO integration

Situation OKTA is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Also it works as Identity Provider that is useful if you want to store credentials outside your service. There are two user groups where SSO integration makes sense: business users and customers. Complexity Hybris OOTB […]

Multi-country content catalogs

 Situation There are N regional websites, one per country. The global marketing teams are responsible for global content. The local marketing teams should be able to manage local content only. Global teams should be able to manage some local content also if they have enough permissions. The system should be idiot-proof, which means that any changes made by […]

Hybris 6 "Could have fired" messages (PoC)

Situation “Could Have Fired” message indicates that the criteria of the promotion has been partially fulfilled. For example, when you have two products in your cart and the promotion for the three products (like buy 3 get 1 free), the ‘could have fired’ message could look like “buy one more product and get one free”. SAP hybris […]