Hybris Architecture

Hybris Commerce suite is highly flexible. It is divided into several packages. These packages are nothing but individual Modules.  All of these packages rely on more basic functionality provided by the hybris Platform.

·       Platfrom

·       PCM

·       Commerce

·       Channel

These packages are bundles of functionality assembled for a certain range of business functionality

Hybris has two architecture

1.       Basic Architecture

2.       Layer Architecture

Basic Architecture

Platform

• Consists of  standard set of extensions
• Hybris server
• Build Framework
• Extension: technical structure of a module, can contain business logic type definition , other database application
• Configuration files
• Platform is the base for every extension.

PCM(Product Cockpit Module )

• One source for all product data
• Sync with external systems well
• Production data publication into different catalog
• Easy to define work flows
• All kind of Import and Export related to data
• Media Management

Commerce

• Sales and  merchandizing for companies (pricing, multi-brand, multi-store, tax management, etc )
• Marketing (Promotions, coupons , etc )
• Multi channel publishing
• E-commerce services(order, customer support, warehousing)

Channel

• Mobile

              Mobile web store integration
              Store Locator
              WCMS integration

• Customer service

              Call center application
              Pre and Post order process at finger tips
              Compartible with low end machines

• Print

              Supports all means of automation publications

• WCMS

              Multi-Store scenarios
              User interface for static and dynamic web site content

Overview diagram of basic architecture

Layer Architecture

The hybris Commerce Suite contains several layers, each of which has a different function and data abstraction level.

• Cockpits, hmc, WebServices:

Layer which interacts with front user, where objects are represented for interaction like: add to cart, product description, passwords for user account this layer basically lets user to play with an object in hybris platform via graphical user interface

This enables organizations to manage about structure information and catalogs in high-volume and collaborative environments.

• ServiceLayer Framework  and Infrastructure Services:

Provides the Java Application Programmer's Interface (API) for objects in the hybris Commerce Suite, the hybris API. The hybris ServiceLayer relies on so-called models, which are pojo objects. Business logic is written is this layer with other functionality such as Pricing, Classifications, Security, Transactions, Sessions

• Type layer:

Definitions of Business objects and their attributes are made on this layer in the form of item.xml file.    

• Persistence Layer:

Deals with the abstraction of Data from database, caching, clustering. We generally do not get in contact with this layer as it is transparent and does not require any interaction from our side.

• Database:

Database is an important component in hybris as it makes the data held in hybris commerce suite .

We can configure any database. By default hybris follows hsql as a database.

Note: Hybris uses layer architecture to keep the data segregated.  Specific layer for specific data to work upon.