Five reasons to choose SAP Spartacus as the implementation framework of SAP commerce cloud storefront

If you have read SAP Commerce Cloud Project Spartacus introduction , You may still want to know more about why you should use based on Project Spartacus Store as SAP Commerce Cloud Part of the solution to move or start your project . In this paper , We will share and act as Accelerator Part of the store is based on JSP Compared to the template , Use Project Spartacus Some of the main advantages of .

Reason #1 - Decoupled Architecture

SAP Commerce Cloud REST API Improved to be fully compatible with any JavaScript Storefront Technology , Allows you to completely separate front-end and back-end development .

Due to the rapid development of front-end technology framework in the past decade , Use jQuery Is no longer enough . Front end developers want to be able to use the main Javascript (JS) One of the frames , for example Angular、React or Vue.js.

The gap between front-end and back-end technologies has widened . Now , You should not expect the same developer to have all the skills needed to efficiently develop both aspects of the solution . You may want to separate your concerns into different teams , To improve productivity and scalability .

Through decoupling architecture , The team can work independently in its own release cycle . for example , You may want to develop on the same day 、 Test and deploy to production UI Make many appearance changes . You can use lightweight solutions （ For example, through REST The service is connected to SAP Commerce Cloud Back end Spartacus） It's easy to achieve that .

Reason #2 - Open Source

Spartacus It's from SAP Commerce Cloud Developed by the same team working on , But the product has been released under an open source license . You will benefit from Project Spartacus All the development work invested by the development team , And your team doesn't need any new investment .

By open source , It should also provide for SAP Commerce Cloud The ecological system 、 Digital institutions and may not be SAP More visits from official partners . Explore... With easy access to code 、 Test and modify the store , You can develop... Faster . Open source projects run using agile models , Allow quick publishing and quick changes （ The goal is ： Every two weeks ）. meanwhile , You have the flexibility to configure settings to automatically introduce new versions , Or you can set up to maintain a specific version of the library .

Even though SAP Managing open source projects , but SAP Keen to welcome contributors and cultivate an inclusive 、 An active development community . This means that customers and partners have direct access to Spartacus The team , Can affect the priority of new features , And can be in our Slack Work area or Stack Overflow Upward Developer 、 Product owners and architects release issues , with “spartacus” label .

Reason #3 - Upgradable and Extensible

since 2019 year 6 Published in 1.0 Since Edition ,Spartacus Designed to ensure that most pages and components implement SAP Commerce Cloud、B2C Accelerator and SAP Commerce Cloud、B2B The function of the accelerator is the same （ Refer to the roadmap to see which features may still be missing ）.

Of course , You are free to add your own components or design new components . According to design ,Spartacus Is modular and extensible , So you can constantly upgrade and benefit from the latest version of components .

Spartacus Pack into a group Angular library , So when new features or fixes are introduced , You can use them immediately . We don't recommend that you fork out when you want to build a new store Spartacus Project or copy / Paste the source code . contrary , You should create a new Angular Application and report to Spartacus Add dependencies to the library . Spartacus Patches and minor versions of should not break compatibility . As long as there is no major version （ for example 2.0、3.0）, Upgrading to the new library will not cause any problems in your store application .

Reason #4 - CMS-Driven

Spartacus The content of the page is from SAP Commerce Content Management System (CMS) Acquired , So content managers can use SAP Commerce Cloud CMS Tools （ Such as SmartEdit） Modify page content . SmartEdit Get full support , And with Project Spartacus Combine to provide a relevant and personalized experience , Include a preview of the site to be displayed to the customer later .

Theoretically , You can even put Spartacus and SAP Commerce Cloud With a third party CMS Use it together . If you have implemented this or similar scenario , We hope you will cooperate with Spartacus Share your results with the community .

Reason #5 - Supported by SAP Commerce Cloud Automation

stay SAP Commerce Cloud In the portal , You can use Project Spartacus Store deployment to public cloud infrastructure . In the public cloud SAP Commerce Cloud Standard build automation support JavaScript Store deployment , Can be independent of SAP Commerce Cloud The solution is built and deployed on a dedicated node .

Besides ,SAP Commerce Cloud Support server side rendering (SSR), Therefore, web crawlers can actively browse your website .