How does Spartacus match with SAP Commerce Cloud (CCV2)?
CCV2 stands for Cloud Commerce Version 2. It is SAP’s new way of marketing and operating the Commerce platform in their own azure cloud. SAP has already rebranded itself to a “cloud company” some time ago and now works consequently on transferring all on-premise customers to CCV2.
In case of CCV2 hosting one would expect that Spartacus is deployed into SAP’s cloud as an independent application. As we discussed in the first part, one of the biggest advantages of a decoupled frontend is the fact that the PWA may be developed independently of a backend. Thus, it may also be released more often utilizing a different pipeline. It makes a lot of sense since the frontend changes are much more frequent and less at risk to break the system than the updates of the backend.
Therefore, it is highly disappointing that at the time of writing this article (May 2021) such independent frontend deployment is still not possible with Spartacus and CCV2. You cannot benefit from independent pipelines.
In order to deploy a new version of your Spartacus-based frontend you will also have to deploy the whole backend. The operation, which shouldn’t need more than a few minutes to complete, may require an hour.
But even more problematic is the fact that, due to the use of common repository, it is difficult to make sure that only frontend is frequently deployed while backends undergo more thorough testing and follow more conservative release cycle.
Of course, this shortcoming is related more to SAP Cloud limitations and not to the Spartacus framework itself. However, as both products are often offered together we wouldn’t expect such issues. We will be happy to update you when this problem is removed.