OCC Layer with a separated storefront like React or AngularJS

[#1]

Hi there,

I would like to st little discussion about topic described in the title.

Did somebody already made some experience with this kind of architecture?

What's are pros and cons of this architecture?

My Pros:

• easier to extend and maintain

• client-side rendering (higherperformance)

• the storefront is separated from the backend

• the storefront could be deployed separated

• the OCC layer could be reused from other platforms

My Cons:

• No hybris standard

• Hybris CMS doesn't work anymore (You have to build your own interfaces)

• What will happen if the framework will be not supported anymore

• Not many frontend developers are available at the moment

• possible Security Risks, because the code will be executed on the client

• possible Performance Issues on the OCC side

Many thanks for answers!

Greetz

[Former Member]

Hi Dominik,

I have used OCC with Backbone.js application. In Hybris 6.0, you have cms web service through which you can expose CMS related information. Prior to that, there were limitations in handling CMS contents.

You have rightly pointed out most of the pros and cons. With this model, you loose the flexibility of managing content lifecycle, a better customer experience etc. The CMS system like Hybris WCMS with storefront or Adobe AEM is more suitable for use cases where content plays an important role in the eCommerce landscape. With Javascripts kind of client in "Headless Commerce", the use case should be in a way that content management related functionalities are not of prime importance.

For security and performance issues, sometime API gateway are being used in between front-end and backend OCC layer in case you want to use as public API.

In OCC, you can manage caching at the server layer with Spring. You can also send Etag related information to client. So, some bit of performance can be managed though OCC layer. The version 6.0 of Hybris seems to be more matured in these aspects.