About Hybrid Deployment Mode for SAP Commerce Cloud UI

The so-called hybrid deployment mode means that part of the Commerce Cloud Storefront UI is served through Spartacus, and the rest is still served through the traditional Accelerator.

example:

• http://localhost:4200/electronics-spa/en/USD/Open-Catalogue/Cameras/Digital-Cameras/c/575 via Spartacus

• http://localhost:4200/electronics-spa/en/USD/cart via Accelerator

Using external route can solve this problem:

ConfigModule.withConfig({
    
    
  routing: {
    
    
    internal: [
      '/',
      '/cart',
      '/product/*/*',
      '/**/p/**',
    ]
  }
})

In SAP Spartacus source code, ConfigModule plays a very important role. ConfigModule is one of the core modules of the Spartacus framework, which is used to manage the configuration information of the entire application. It provides a mechanism for centrally managing and loading configurations to ensure correct operation and configuration of applications in different environments. The role and function of ConfigModule will be introduced in detail below.

1. Loading application configuration:
   ConfigModule is responsible for loading and managing application configuration information. In Spartacus, application configuration is divided into two levels: default configuration and environment-specific configuration. Default configurations are general settings for the application, while environment-specific configurations contain settings related to a specific environment, such as development environment, production environment, etc. The ConfigModule is responsible for loading these configurations and merging them in order to provide the correct configuration at runtime.

2. Manage configurations for different environments:
   Spartacus applications need to run in different environments, such as development, test, and production. Each environment may have different configuration needs, such as the base URL of the backend API, authentication tokens, etc. ConfigModule allows developers to provide appropriate configurations for specific environments and easily switch configurations as needed. This allows applications to run correctly in different environments and allows for easy configuration management.

3. Provide configuration override mechanism:
   ConfigModule supports configuration override mechanism, which means developers can override the default configuration in a specific environment. For example, if you need to modify a certain default configuration value in a specific environment, you can override it by providing the corresponding specific environment configuration. This allows flexibility in the configuration of the application and the ability to customize it to the needs of different environments.

4. Integrate third-party configuration:
   ConfigModule also provides the ability to integrate third-party configuration. It allows developers to integrate third-party configurations into applications to meet the needs of specific functions or modules. For example, if you need to integrate Google Analytics or other analysis tools, you can integrate its configuration into the application through the ConfigModule.

5. Configuration injection and access:
   ConfigModule provides a convenient way to inject and access application configuration. By injecting ConfigModule in components or services that need access to configuration, developers can easily obtain configuration information and use it in the application. In this way, configuration information can be passed and shared throughout the application to meet the needs of different modules and components.

6. Support multilingual configuration:
   Spartacus framework supports multilingual applications, and ConfigModule provides corresponding support and management mechanisms. Developers can configure multilingual settings through ConfigModule, such as default language, list of supported languages, etc. This enables applications to serve localized content according to the user's language preference.