An overview to hybris Commerce Suite architecture

**UPDATED, March 4, 2015, after a mistaken early publish :-(**

Now that we got through on where content of hybris Blank comes from and how to configure your own local environment, we now begin actually diving into hybris, what we are all here for any way. 🙂

Before I go further, I would be remissed if I did not mention superb training courses already provided by hybris. hybris has established several training courses for decision makers, business analysts and developers. For complete list of courses, descriptions and associated pricing, checkout hybris Education Space (wiki.hybris.com account required).

In this article I will discuss the high-level segments of hybris Commerce Suite that we will be interacting with and provide examples of extensions and modules within each segment.

The hybris Commerce Suite is explained fairly well in the Architecture Overview page in the hybris wiki site (http://wiki.hybris.com) for both Business and Technical audiences. I am going to recap it below and add additional thoughts inline.

cake - overall (1)

Above image was created by hybris and commonly used in many of their documentations (rightfully so, it provides a very clear business picture of the Suite). Let me break the terms in the picture down a little further, as some terms can be subjective (or if you are new to commerce platforms, could be new to you), so let’s walk around the circle first:

  • Content: Content is in essence the core information of your site, more specifically information related to the products you will be selling. This includes
    • Product Catalogs
    • Product Categories and Classification System
    • Media (such as product images)
  • Orders: Orders is just like it sounds. This is the layer that contains all details related to ordering of your products, including
    • Promotions
    • Payment and fulfillment details
    • Inventory management
    • Order history and management
    • Customer details
  • Channel: Channel refers to how you actually reach your customers. This can be a mix of both digitial and physical methods such as
    • Web store (Desktop and Mobile interfaces)
    • InStore kiosks
    • Printed media
    • Email
  • Commerce: Commerce component provides a collection of modules (features/functions) based on the type commerce site you are running. Per typical commerce sites, hybris provides 2 types depending on the type of client you plan to serve:
    • B2C (Business to Consumer), B2C is for businesses looking to sell to individuals. B2C has a large collection of touchpoint options and look to provide the customer easy method to find, learn and purchase products.
    • B2B (Business to Business), B2B is when business is looking to sell to another business. Essentially involves orders containing large quantities of single product sales with communication and approval processes between ecommerce platform and procurement systems. It also typically involves establishment of quotes and potentially negotiations on finalized deals.
  • Platform: Platform is the final component and is the core architecture of the Suite, where the application interface and infrastructure resides.

From a technical perspective, I really cannot add more than what you can already find in the Architecture Overview page and suggest you jump over to take a short read. 🙂

Before I close out this article on Architecture, I’d like to clarify some terms to try and minimize confusion in future:

  • hybris Commerce Suite This is what we spoke about above. There is two variations of the Suite, which include
    • hybris B2C Commerce
    • hybris B2B Commerce
  • hybris Commerce Accelerator is a pre-built solution provided by hybris that is build on top of the hybris Commerce Suite. This is a great starting point for companies seeking a faster time to market solution. The hybris Commerce Accelerator has its limitations though in some areas, and depending on your needs, you or your hybris Partner might chose to start from a clean slate, this is acceptable and quite possible necessary. If it is chosen to bypass the hybris Commerce Accelerator, this does not by any means downgrade the power of hybris, nor change the architecture I mentioned earlier in any way.
  • Extensions is a new feature introduced into your hybris Commerce Suite its capability. hybris provides many extensions and hybris Partners develop these as well. What is great about hybris architecture is that the extension is self contained to minimize potential impact of bad implementation and improves stability of the core platform for future updates.

In future articles, I will continue to introduce new terms as well.

Advertisements

10 thoughts on “An overview to hybris Commerce Suite architecture

  1. Pingback: Product Catalogs… And no, I’m not the IKEA Catalog at home catalogs! | hybris Blank

    1. Jeff Kozloff Post author

      Thanks for the support! sorry for no additional articles. Been working on a into to ecommerce training for some time. Hope to release it soon then come back to hybris blank.

      Like

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s