Why Migrate your Hybris Commerce Storefront to Spartacus?

Spartacus is JavaScript-based Storefront technology that allows you to build a headless commerce Storefront much like a Single Page Website (SPA) for SAP Commerce Cloud. In this article, I will provide you with a few reasons to seriously consider using Spartacus for your B2C and B2B storefronts.

Headless Architecture

As per the latest trends, more and more Storefronts are deployed in a headless fashion. The front end UI is decoupled from the core commerce capabilities. I have explained headless commerce and its advantages in my previous blog. Please refer (https://www.linkedin.com/pulse/headless-commerce-explained-sanjjeev-k-singh/). 

Due to the ever-expanding gap between front-end and back-end technologies, it is recommended that you run your Storefront in a decoupled manner. You are able to update your Storefront UI and offer the best customer experience, independent of your backend system and applications. As the front-end and back-end are decoupled, teams can work independently with their own release cycles. You can easily update and deploy UI changes without worrying about your Commerce platform. Spartacus Javascript Storefront leverages REST-Services available out-of-the-box in SAP Commerce Cloud. Various commerce capabilities such as product catalog, pricing, stock, shopping cart, checkout, order details, etc can be easily offered through the Commerce Cloud platform. With a Spartacus based UI, you are setting the foundation for a Headless Commerce Architecture.

Content Driven

You can use native SAP Commerce Cloud CMS like SmartEdit, or from a 3rd party CMS like e-Spirit to retrieve contents. If SmartEdit does not meet your CMS requirements, you can use the e-Spirit CMS solution supported by Spartacus. ASAR has performed Spartacus integration with e-Spirit CMS using standard API integration. In a Spartacus based site, your content is delivered from the CMS of your choice, either native SAP Commerce Cloud CMS (SmartEdit) or any 3rd party CMS. 

 SAP Commerce Cloud Support

SAP Commerce Cloud supports the build automation and deployment capabilities out of the box with Spartacus storefront. You can easily deploy your Spartacus storefront on the Public Cloud infrastructure (as SAP Commerce Cloud). You can support the build and deployment of your Spartacus Storefront on dedicated nodes independent of the SAP Commerce Cloud solution. Also, Spartacus JavaScript Storefront supports web crawlers to easily browse your website as SAP Commerce Cloud supports server-side rendering.  

Open Source

Though Spartacus is developed by the same team as SAP Commerce Cloud, this product is released with an Open Source license. You can leverage Spartacus and all the future enhancements to it without worrying about any licensing costs. You can access the Spartacus code to explore, test, and modify a Storefront as needed. The Spartacus project is run by SAP using Agile methodology, with 2 weeks’ release and update cycles.

Upgrade and Extension

Spartacus is designed to be modular and extensible. You can continuously upgrade and benefit from the latest version of components. You are also free to design and add your own components. Spartacus is offered as a packaged set of Angular libraries to extend you the advantage of receiving new features and fixes as soon as they are available. You are recommended not to copy and paste the source code when you build a new Storefront. Rather, you should create a new Angular app and add dependencies to the Spartacus libraries.

If you would like to explore what it would take to migrate your B2B or B2C Accelerator-based Storefront to Spartacus, please contact us. The SAP Commerce team at ASAR would love to help you migrate to Spartacus as quickly and efficiently as possible. I hope this blog was helpful. Please feel free to share your comments. For details on Spartacus, please contact Team ASAR.

Author avatar

Post a comment

Your email address will not be published. Required fields are marked *

We use cookies to give you the best experience.