Monthly Archives: May 2018
I thought it would be really great to know more about Oracle Commerce.
So I decided to learn it better, and fix my thoughts and conclusions in the form of comparison with what I know about SAP Hybris Commerce. Yes, it is still a Hybris blog, but…
I’ve been participating in negotiations on what platform is better suited for customer’s needs. Understanding both Oracle Commerce and SAP Hybris really counts. I participated in many meetings in my past where nobody in the room was able to compare the products properly. Oracle people big up their products without clear understanding of pros and cons of SAP Hybris, and SAP managers behave in the same way. The partners are generally good at any one thing.
I hope the information below will help you to picture your own understanding. I was trying to be as objective as I can. Despite the fact the blog is hybris-centered, all strengths of Oracle Commerce are clearly highlighted and all weaknesses of Hybris are present too.
In this document, I am going to compare four e-commerce products:
SAP Hybris Commerce On Premise
SAP Hybris Commerce Cloud
Oracle Commerce (ex-ATG) On Premise
Oracle Commerce Cloud
Out-of-the-box SAP Commerce hybris extensions are great examples of how to customize the platform delivered directly from SAP. They can be used as a reference of implementation and can be considered as a vendor-recommended best-practice way.
The extensions come in source code form, with comments and documentation. It is a good starting point in finding a solution: the way SAP recommends in their packaged extensions is likely better than anything else, because you never know what side effects you may face if you go with the experimental solution. After all, why to reinvent the wheel?
Learning by examples and design by examples have a lot in common. You can use this approach to upskill junior developers and perfect your own expertise. For me personally, there is no other way to learn solution architecture other than studying the experience of others.
The purpose of this document is to shed a light on the internal data structures used by SAP Hybris Commerce. I explain system tables and attributes, their purpose and meaning.
Understanding of the internal structure is very useful in troubleshooting and low-level data analysis. For example, direct access to the database may show that your system has a lot of unused items, and it affects the performance. Analyzing the data is also extremely helpful with data integrity issues.