Product cockpit performance and scalability and deployment approach

[former_member671622]

Hi,

Need guidance on quality attributes like performance and scalability of product cockpit.

Performance:

How to increase the 'Performance' in product cockpit, in terms of 1.Browsing 2. Searching, 3. Synchronization. 4. Importing (huge products 1 million)

Apart from, 1. productcockpit.default.catalogBrowser.maxEntries=1000 2. Multi-threaded synchronization 3.Since the product values will be changing frequently, caching is not really useful in product cockpit.

what are the other things need to be considered to increase the performance in product cockpit, I could think of replacing default product search with solr search, which is available in cscockpit, why it is not available as alternate search service in product cockpit.

Scalability

1. We have 1 million products at present, and in near future we are expecting another 1 million products, how scalable is product cockpit ?

2. Will the search, browse and other actions will not increase the load in database? Will this load decrease the website performance?(assuming both pcm and commerce are deployed/using the same database instance)

3. To overcome point no 2, Is it ok to deploy PCM in a separate instance and commerce in separate instance?In this way PCM can scale separately (scale-in/scale-out) and will not increase the load in commerce database.

Kindly let me know the whether the approach is right or not.

Thanks, Arun

[Former Member]

1. How scalable is the product cockpit? Product Cockpit has been used with 20 million SKUs but we weren't using the DB for search

2. Will the search, browse and other actions will not increase the load in database? Yes it will although using a search engine (e.g. Solr) will help a lot. Still, changes make to product content is invalidating both the query and entity cache used by the front end. If the business is planning to make heavy use of the PCM tool then this is an important considerable for separating PCM and Commerce.

3. To overcome point no 2, Is it ok to deploy PCM in a separate instance and commerce in separate instance? Yes, this has been done before even if PCM and Commerce as both hybris systems. It does add some extra complexities however.

Here are some pros and cons for separate PCM and Commerce

Pros - Back office changes in the PCM are not affecting Commerce performance - Intensive backend jobs can be run during business hours - Can have a different release schedule for PCM functionality

Cons - No standard synchronisation between 2 hybris systems (Professional Services have experience here) - We cannot preview product content on the front end until we publish to the commerce system (minor issue) - More hardware will be required - 2 environments to maintain

[former_member671622]

Thanks for the response brendan !.

Is hybris professional services using ETL tools like Talend for synchronization between 2 hybris systems or a bespoke development ?. Can't we use DataHub to achieve this?

[Former Member]

DataHub is currently only handling the import of data. What you could create a customer exporter or use an ETL tool to pass the data through the data hub and into the hybris commerce system.

PS have a custom solution natively publishes data between 2 hybris systems without the need of any middleware.