{"@attributes":{"version":"2.0"},"channel":{"title":"Spryker Documentation","description":"Spryker documentation center.","link":"https:\/\/docs.spryker.com\/","lastBuildDate":"Fri, 03 Apr 2026 12:40:38 +0000","generator":"Jekyll v4.2.2","item":[{"title":"Keeping dependencies updated for performance","description":"Keeping your project's Spryker module dependencies up to date is critical for maintaining optimal performance, security, and reducing long-term upgrade efforts.\n\n## Why keep dependencies updated\n\nUpdating dependencies regularly provides several practical benefits:\n\n1. **Risk of security vulnerabilities**: Most recent versions contain necessary fixes to all known vulnerabilities.\n2. **Performance and resource consumption optimizations**: Spryker continuously releases performance improvements based on real-life experiences and scenarios.\n3. **Decreasing upgrade efforts**: Distributing upgrades across many smaller steps is much easier than doing one massive upgrade later.\n\n## Key resources\n\nThe following resources provide information about performance-related module releases:\n\n- [Security release notes 202512.0](https:\/\/docs.spryker.com\/docs\/about\/all\/releases\/security-releases\/security-release-notes-202512.0.html)\n- [Release notes 202410.0](https:\/\/docs.spryker.com\/docs\/scos\/user\/intro-to-spryker\/releases\/release-notes\/release-notes-202410.0\/release-notes-202410.0.html)\n- [Release notes 202507.0](https:\/\/docs.spryker.com\/docs\/scos\/user\/intro-to-spryker\/releases\/release-notes\/release-notes-202507.0\/release-notes-202507.0.html)\n- [General performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/general-performance-guidelines.html) - contains the list of recent module versions with known performance optimizations\n- [Cart page performance configuration](https:\/\/docs.spryker.com\/docs\/pbc\/all\/cart-and-checkout\/latest\/cart-page-performance-configuration.html)\n\n## Critical module updates\n\nThe following sections list important module updates that include performance improvements. It's recommended that each Spryker project evaluates and applies these updates.\n\n### Product search performance\n\n**spryker\/product-page-search** - Recent versions (for example, `3.38.0` - `3.40.0`) include improvements such as:\n- Caching logic adjustments for product images\n- Potential bulk operation support to make search document writes more efficient\n- Avoiding duplicate locale events\n\n### Session management\n\n**spryker\/session** - at least `^4.17.0`\n- Provides configurable session locking mechanism\n- See [Redis session lock](\/docs\/dg\/dev\/troubleshooting\/troubleshooting-performance-issues\/redis-session-lock.html) for configuration details\n\n**spryker\/session-redis** - at least `^1.11.2`\n- Includes configurable session locker\n- See [Redis session lock](\/docs\/dg\/dev\/troubleshooting\/troubleshooting-performance-issues\/redis-session-lock.html) for setup instructions\n\n### Merchant Portal and Back Office performance with ACL rules\n\n- [spryker\/acl:^3.26.0](https:\/\/github.com\/spryker\/acl\/releases\/tag\/3.26.0)\n- [spryker\/acl-entity:^1.16.0](https:\/\/github.com\/spryker\/acl-entity\/releases\/tag\/1.16.0)\n- [spryker\/gui:^4.11.0](https:\/\/github.com\/spryker\/gui\/releases\/tag\/4.11.0)\n- [spryker\/merchant-profile:^1.9.0](https:\/\/github.com\/spryker\/merchant-profile\/releases\/tag\/1.9.0)\n- [spryker\/merchant-user:^1.9.0](https:\/\/github.com\/spryker\/merchant-user\/releases\/tag\/1.9.0)\n- [spryker\/multi-factor-auth-merchant-portal:^2.1.0](https:\/\/github.com\/spryker\/multi-factor-auth-merchant-portal\/releases\/tag\/2.1.0)\n- [spryker\/product-attribute:^1.18.0](https:\/\/github.com\/spryker\/product-attribute\/releases\/tag\/1.18.0)\n- [spryker\/zed-navigation:^1.15.0](https:\/\/github.com\/spryker\/zed-navigation\/releases\/tag\/1.15.0)\n\n### Back Office performance on category list page\n\n- [spryker\/product-category:\"^4.32.0\"](https:\/\/github.com\/spryker\/zed-navigation\/releases\/tag\/4.32.0)\n\n### Order placement performance\n\n- [spryker\/calculation:^4.14.0](https:\/\/github.com\/spryker\/calculation\/releases\/tag\/4.14.0)\n- [spryker\/discount-calculation-connector:^5.4.0](https:\/\/github.com\/spryker\/discount-calculation-connector\/releases\/tag\/5.4.0)\n- [spryker\/merchant:^3.15.0](https:\/\/github.com\/spryker\/merchant\/releases\/tag\/3.15.0)\n- [spryker\/sales:^11.60.0](https:\/\/github.com\/spryker\/sales\/releases\/tag\/11.60.0)\n- [spryker\/product:^6.49.0](https:\/\/github.com\/spryker\/product\/releases\/tag\/6.49.0)\n- [spryker\/discount:^9.43.0](https:\/\/github.com\/spryker\/discount\/releases\/tag\/9.43.0)\n- [spryker\/product-cart-connector:^4.13.0](https:\/\/github.com\/spryker\/product-cart-connector\/releases\/tag\/4.13.0)\n- [spryker\/company-role:^1.9.1](https:\/\/github.com\/spryker\/company-role\/releases\/tag\/1.9.1)\n- [spryker\/propel:^3.43.0](https:\/\/github.com\/spryker\/propel\/releases\/tag\/3.43.0)\n- [spryker\/sales:^11.63.0](https:\/\/github.com\/spryker\/sales\/releases\/tag\/11.63.0)\n- [spryker\/sales-product-connector:^1.11.1](https:\/\/github.com\/spryker\/sales-product-connector\/releases\/tag\/1.11.1)\n- [spryker\/shipment:^8.24.0](https:\/\/github.com\/spryker\/shipment\/releases\/tag\/8.24.0)\n\n### OMS availability check and order item reservation\n\n- [spryker\/availability:^9.27.0](https:\/\/github.com\/spryker\/availability\/releases\/tag\/9.27.0)\n- [spryker\/stock:^8.10.1](https:\/\/github.com\/spryker\/stock\/releases\/tag\/8.10.1)\n- [spryker\/oms:^11.45.1](https:\/\/github.com\/spryker\/oms\/releases\/tag\/11.45.1)\n- [spryker\/propel:^3.43.0](https:\/\/github.com\/spryker\/propel\/releases\/tag\/3.43.0)\n- [spryker\/sales:^11.63.0](https:\/\/github.com\/spryker\/sales\/releases\/tag\/11.63.0)\n\n### Publish and synchronization (merchant-related)\n\n- [spryker\/merchant-product-offer-storage:^2.6.0](https:\/\/github.com\/spryker\/merchant-product-offer-storage\/releases\/tag\/2.6.0)\n- [spryker\/product-offer-storage:^1.8.0](https:\/\/github.com\/spryker\/product-offer-storage\/releases\/tag\/1.8.0)\n- [spryker\/propel:^3.45.0](https:\/\/github.com\/spryker\/propel\/releases\/tag\/3.45.0)\n\n### Publish and synchronization (product-related)\n\n- [spryker\/price-product:^4.48.0](https:\/\/github.com\/spryker\/price-product\/releases\/tag\/4.48.0)\n- [spryker\/product-page-search:^3.40.0](https:\/\/github.com\/spryker\/product-page-search\/releases\/tag\/3.40.0)\n- [spryker\/product-search:^5.24.1](https:\/\/github.com\/spryker\/product-search\/releases\/tag\/5.24.1)\n- [spryker\/product-storage:^1.47.0](https:\/\/github.com\/spryker\/product-storage\/releases\/tag\/1.47.0)\n- [spryker\/product-offer-storage:^1.10.0](https:\/\/github.com\/spryker\/product-offer-storage\/releases\/tag\/1.10.0)\n- [spryker\/price-product-offer:^1.7.1](https:\/\/github.com\/spryker\/price-product-offer\/releases\/tag\/1.7.1)\n- [spryker\/price-product-offer-storage:^1.5.1](https:\/\/github.com\/spryker\/price-product-offer-storage\/releases\/tag\/1.5.1)\n- [spryker\/price-product-storage:^4.13.0](https:\/\/github.com\/spryker\/price-product-storage\/releases\/tag\/4.13.0)\n- [spryker\/product-image:^3.20.1](https:\/\/github.com\/spryker\/product-image\/releases\/tag\/3.20.1)\n- [spryker\/product-category-storage:^2.11.0](https:\/\/github.com\/spryker\/product-category-storage\/releases\/tag\/2.11.0)\n- [spryker\/product-category-search:^1.2.1](https:\/\/github.com\/spryker\/product-category-search\/releases\/tag\/1.2.1)\n- [spryker\/propel:^3.47.0](https:\/\/github.com\/spryker\/propel\/releases\/tag\/3.47.0)\n - Note: If you still use destructive deployments, update the `config\/install\/destructive.yml` file. You can copy it from any demo shop.\n- [spryker\/event-behavior:^1.32.0](https:\/\/github.com\/spryker\/event-behavior\/releases\/tag\/1.32.0)\n- [spryker\/synchronization-behavior:^1.13.0](https:\/\/github.com\/spryker\/synchronization-behavior\/releases\/tag\/1.13.0)\n\n### Publish and synchronization (Category tree build logic)\n\n- [spryker\/category:\"^5.23.0\"](https:\/\/github.com\/spryker\/category\/releases\/tag\/5.23.0)\n- [spryker\/category-storage:\"^2.12.0\"](https:\/\/github.com\/spryker\/category-storage\/releases\/tag\/2.12.0)\n- [spryker\/propel-orm:\"^1.22.0\"](https:\/\/github.com\/spryker\/propel-orm\/releases\/tag\/1.22.0)\n- [spryker\/util-sanitize:\"^2.3.1\"](https:\/\/github.com\/spryker\/util-sanitize\/releases\/tag\/2.3.1)\n\n### Data import (memory usage)\n\n- [spryker\/acl-entity:\"^1.17.0\"](https:\/\/github.com\/spryker\/acl-entity\/releases\/tag\/1.17.0)\n- [spryker\/data-import:\"^1.33.0\"](https:\/\/github.com\/spryker\/data-import\/releases\/tag\/1.33.0)\n- [spryker\/merchant-relationship-product-list-data-import:\"^0.1.3\"](https:\/\/github.com\/spryker\/merchant-relationship-product-list-data-import\/releases\/tag\/0.1.3)\n- [spryker\/price-product-merchant-relationship-data-import:\"^0.2.5\"](https:\/\/github.com\/spryker\/price-product-merchant-relationship-data-import\/releases\/tag\/0.2.5)\n\n### Cart page and checkout for large carts (100+ items)\n\nFor comprehensive guidance on optimizing cart performance, see [Cart page performance configuration](https:\/\/docs.spryker.com\/docs\/pbc\/all\/cart-and-checkout\/latest\/cart-page-performance-configuration.html).\n\n## Update strategy\n\nTo effectively manage dependency updates:\n\n1. **Monitor release notes**: Regularly check Spryker release notes for performance-related updates.\n2. **Test in staging**: Always test module updates in a staging environment before production deployment.\n3. **Prioritize performance modules**: Focus on modules that directly impact your application's performance bottlenecks.\n4. **Use semantic versioning**: Understand the impact of major, minor, and patch updates.\n5. **Batch related updates**: Group related module updates together for testing efficiency.\n\n## Compatibility considerations\n\nWhen updating modules:\n\n- Check module compatibility with your current Spryker version\n- Review breaking changes in major version updates\n- Test all affected functionality after updates\n- Monitor application performance metrics before and after updates\n- Consider using Spryker's [Composer Dependency Manager](https:\/\/docs.spryker.com\/docs\/scos\/dev\/setup\/managing-scos-dependencies-with-composer.html)\n","pubDate":"Fri, 03 Apr 2026 11:08:16 +0000","link":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/keeping-dependencies-updated.html","guid":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/keeping-dependencies-updated.html"},{"title":"Split publish queues for performance","description":"By default, all publish events are routed through a single generic queue (`PublisherConfig::PUBLISH_QUEUE`). This document explains how to migrate to dedicated per-module queues to improve processing throughput and system stability.\n\n## Benefits\n\nSplitting the publish queue into dedicated per-module queues provides the following benefits:\n\n- **Predictable bulk processing**: Each queue processes a specific type of message, enabling bulk processing instead of random small batches that depend on message arrival order.\n- **Fault isolation**: If one queue becomes stuck, only that specific message type is affected \u2014 not the entire system.\n- **Better resource utilization**: Dedicated queues let you use powerful instances more effectively.\n- **Scalability for all project sizes**: Even small projects benefit from faster and more predictable queue processing.\n\n## Potential issues\n\nSplitting queues can spawn a large number of tasks. To prevent resource exhaustion, configure the maximum number of background processes for both the standard worker and the resource-aware worker in `config\/Shared\/config_default.php`:\n\n```php\n$config[QueueConstants::QUEUE_WORKER_MAX_PROCESSES] = 5;\n```\n\nSet this value according to the resources available on your infrastructure.\n\n{% info_block warningBox \"Worker task limits\" %}\n\nBoth the standard queue worker and the resource-aware queue worker enforce the `QUEUE_WORKER_MAX_PROCESSES` limit on the number of tasks executed in the background. Tune this value carefully based on available CPU and memory.\n\n{% endinfo_block %}\n\n## Install the optimization\n\n```bash\ncomposer update \\\n spryker\/rabbit-mq:\"^2.23.1\" \\\n spryker\/category-image-storage:\"^1.9.0\" \\\n spryker\/cms-page-search:\"^2.10.0\" \\\n spryker\/cms-storage:\"^2.11.0\" \\\n spryker\/company-user-storage:\"^1.7.0\" \\\n spryker\/configurable-bundle-page-search:\"^1.6.0\" \\\n spryker\/configurable-bundle-storage:\"^2.8.0\" \\\n spryker\/content-storage:\"^2.8.0\" \\\n spryker\/customer-access-storage:\"^1.13.0\" \\\n spryker\/file-manager-storage:\"^2.6.0\" \\\n spryker\/merchant-product-offer-search:\"^1.8.0\" \\\n spryker\/navigation-storage:\"^1.14.0\" \\\n spryker\/price-product-merchant-relationship-storage:\"^1.20.0\" \\\n spryker\/price-product-offer-storage:\"^1.7.0\" \\\n spryker\/product-alternative-storage:\"^1.14.0\" \\\n spryker\/product-category-filter-storage:\"^1.7.0\" \\\n spryker\/product-discontinued-storage:\"^1.18.0\" \\\n spryker\/product-group-storage:\"^1.8.0\" \\\n spryker\/product-list-search:\"^2.10.0\" \\\n spryker\/product-list-storage:\"^1.20.0\" \\\n spryker\/product-measurement-unit-storage:\"^1.16.0\" \\\n spryker\/product-offer-availability-storage:\"^1.5.0\" \\\n spryker\/product-option-storage:\"^1.16.0\" \\\n spryker\/product-packaging-unit-storage:\"^5.4.0\" \\\n spryker\/product-page-search:\"^3.46.0\" \\\n spryker\/product-quantity-storage:\"^3.7.0\" \\\n spryker\/product-review-search:\"^1.15.0\" \\\n spryker\/product-review-storage:\"^1.9.0\" \\\n spryker\/product-search-config-storage:\"^1.7.0\" \\\n spryker\/product-set-page-search:\"^1.14.0\" \\\n spryker\/product-set-storage:\"^1.15.0\" \\\n spryker\/queue:\"^1.24.0\" \\\n spryker\/queue-extension:\"^1.2.0\" \\\n spryker\/shopping-list-storage:\"^1.10.0\" \\\n spryker\/symfony-messenger:\"^1.2.0\" \\\n spryker\/tax-product-storage:\"^1.7.0\" \\\n spryker\/tax-storage:\"^1.7.0\" \\\n spryker\/url-storage:\"^1.22.0\"\n```\n\nRelease group [SOL-486](https:\/\/api.release.spryker.com\/release-group\/6388)\n\nFor a complete project-level implementation example, see the [B2B Demo Marketplace PR #966](https:\/\/github.com\/spryker-shop\/b2b-demo-marketplace\/pull\/966).\n\n## Configure the dedicated queues\n\nThe migration requires changes in three layers: broker registration, queue processor mapping, and per-module configuration.\n\n### 1. Register queues with the message broker\n\nRegister the dedicated queues with your message broker. Depending on your setup, you configure either `RabbitMqConfig` or `SymfonyMessengerConfig` \u2014 not both. If you use Symfony Messenger, see [Integrate Symfony Messenger](\/docs\/dg\/dev\/integrate-and-configure\/integrate-symfony-messenger.html).\n\n**`src\/Pyz\/Client\/RabbitMq\/RabbitMqConfig.php`**\n\nAdd the following `use` statements and queue constants to `getPublishQueueConfiguration()`:\n\n```php\nuse Spryker\\Shared\\CategoryImageStorage\\CategoryImageStorageConfig;\nuse Spryker\\Shared\\CompanyUserStorage\\CompanyUserStorageConfig;\nuse Spryker\\Shared\\MerchantProductOfferSearch\\MerchantProductOfferSearchConfig;\nuse Spryker\\Shared\\PriceProductMerchantRelationshipStorage\\PriceProductMerchantRelationshipStorageConfig;\nuse Spryker\\Shared\\PriceProductOfferStorage\\PriceProductOfferStorageConfig;\nuse Spryker\\Shared\\ProductAlternativeStorage\\ProductAlternativeStorageConfig;\nuse Spryker\\Shared\\ProductCategoryFilterStorage\\ProductCategoryFilterStorageConfig;\nuse Spryker\\Shared\\ProductDiscontinuedStorage\\ProductDiscontinuedStorageConfig;\nuse Spryker\\Shared\\ProductGroupStorage\\ProductGroupStorageConstants;\nuse Spryker\\Shared\\ProductListSearch\\ProductListSearchConfig;\nuse Spryker\\Shared\\ProductListStorage\\ProductListStorageConfig;\nuse Spryker\\Shared\\ProductMeasurementUnitStorage\\ProductMeasurementUnitStorageConfig;\nuse Spryker\\Shared\\ProductOfferAvailabilityStorage\\ProductOfferAvailabilityStorageConfig;\nuse Spryker\\Shared\\ProductOptionStorage\\ProductOptionStorageConfig;\nuse Spryker\\Shared\\ProductPackagingUnitStorage\\ProductPackagingUnitStorageConfig;\nuse Spryker\\Shared\\ProductQuantityStorage\\ProductQuantityStorageConfig;\nuse Spryker\\Shared\\ProductReviewSearch\\ProductReviewSearchConfig;\nuse Spryker\\Shared\\ProductReviewStorage\\ProductReviewStorageConfig;\nuse Spryker\\Shared\\ProductSearchConfigStorage\\ProductSearchConfigStorageConfig;\nuse Spryker\\Shared\\ProductSetPageSearch\\ProductSetPageSearchConfig;\nuse Spryker\\Shared\\ProductSetStorage\\ProductSetStorageConfig;\nuse Spryker\\Shared\\ShoppingListStorage\\ShoppingListStorageConfig;\nuse Spryker\\Shared\\TaxProductStorage\\TaxProductStorageConfig;\n\n protected function getPublishQueueConfiguration(): array\n {\n return [\n \/\/ other queue configs\n CategoryImageStorageConfig::PUBLISH_CATEGORY_IMAGE_QUEUE,\n CompanyUserStorageConfig::PUBLISH_COMPANY_USER_QUEUE,\n MerchantProductOfferSearchConfig::PUBLISH_MERCHANT_PRODUCT_OFFER_QUEUE,\n PriceProductMerchantRelationshipStorageConfig::PUBLISH_PRICE_PRODUCT_MERCHANT_RELATIONSHIP_QUEUE,\n PriceProductMerchantRelationshipStorageConfig::PUBLISH_PRICE_PRODUCT_CONCRETE_MERCHANT_RELATIONSHIP_QUEUE,\n PriceProductMerchantRelationshipStorageConfig::PUBLISH_PRICE_PRODUCT_ABSTRACT_MERCHANT_RELATIONSHIP_QUEUE,\n PriceProductOfferStorageConfig::PUBLISH_PRICE_PRODUCT_OFFER_QUEUE,\n ProductAlternativeStorageConfig::PUBLISH_PRODUCT_ALTERNATIVE_QUEUE,\n ProductCategoryFilterStorageConfig::PUBLISH_PRODUCT_CATEGORY_FILTER_QUEUE,\n ProductDiscontinuedStorageConfig::PUBLISH_PRODUCT_DISCONTINUED_QUEUE,\n ProductGroupStorageConstants::PUBLISH_PRODUCT_GROUP_QUEUE,\n ProductListSearchConfig::PUBLISH_PRODUCT_LIST_SEARCH_QUEUE,\n ProductListStorageConfig::PUBLISH_PRODUCT_LIST_QUEUE,\n ProductListStorageConfig::PUBLISH_PRODUCT_LIST_PRODUCT_ABSTRACT_QUEUE,\n ProductListStorageConfig::PUBLISH_PRODUCT_LIST_PRODUCT_CONCRETE_QUEUE,\n ProductOfferAvailabilityStorageConfig::PUBLISH_PRODUCT_OFFER_AVAILABILITY_QUEUE,\n ProductOptionStorageConfig::PUBLISH_PRODUCT_OPTION_QUEUE,\n ProductQuantityStorageConfig::PUBLISH_PRODUCT_QUANTITY_QUEUE,\n ProductReviewSearchConfig::PUBLISH_PRODUCT_REVIEW_QUEUE,\n ProductReviewStorageConfig::PUBLISH_PRODUCT_REVIEW_STORAGE_QUEUE,\n ProductSearchConfigStorageConfig::PUBLISH_PRODUCT_SEARCH_CONFIG_QUEUE,\n ProductSetPageSearchConfig::PUBLISH_PRODUCT_SET_PAGE_QUEUE,\n ProductSetStorageConfig::PUBLISH_PRODUCT_SET_QUEUE,\n ShoppingListStorageConfig::PUBLISH_SHOPPING_LIST_QUEUE,\n TaxProductStorageConfig::PUBLISH_TAX_PRODUCT_QUEUE,\n ProductMeasurementUnitStorageConfig::PUBLISH_PRODUCT_MEASUREMENT_UNIT_QUEUE,\n ProductPackagingUnitStorageConfig::PUBLISH_PRODUCT_PACKAGING_UNIT_QUEUE,\n ];\n }\n```\n\nIf you use Symfony Messenger instead of RabbitMQ, apply the same changes to `src\/Pyz\/Client\/SymfonyMessenger\/SymfonyMessengerConfig.php`.\n\n### 2. Map queues to processor plugins\n\nUpdate `QueueDependencyProvider` to map each new queue to its processor plugin.\n\n**`src\/Pyz\/Zed\/Queue\/QueueDependencyProvider.php`**\n\nFor each dedicated queue, add a mapping to either `SynchronizationStorageQueueMessageProcessorPlugin` (for storage queues) or `SynchronizationSearchQueueMessageProcessorPlugin` (for search queues). For example:\n\n```php\nCategoryImageStorageConfig::PUBLISH_CATEGORY_IMAGE_QUEUE => [\n new SynchronizationStorageQueueMessageProcessorPlugin(),\n],\nProductReviewSearchConfig::PUBLISH_PRODUCT_REVIEW_QUEUE => [\n new SynchronizationSearchQueueMessageProcessorPlugin(),\n],\n\/\/ ... repeat for all dedicated queues\n```\n\n### 3. Update per-module Zed configuration\n\nFor each module, override the config class at the project level to return the module-specific queue constant instead of the generic `PublisherConfig::PUBLISH_QUEUE`.\n\nThe following table lists the files to update and their corresponding queue constants:\n\n| File | Queue constant |\n|---|---|\n| `src\/Pyz\/Zed\/CategoryImageStorage\/CategoryImageStorageConfig.php` | `CategoryImageStorageConfig::PUBLISH_CATEGORY_IMAGE_QUEUE` |\n| `src\/Pyz\/Zed\/CompanyUserStorage\/CompanyUserStorageConfig.php` | `CompanyUserStorageConfig::PUBLISH_COMPANY_USER_QUEUE` |\n| `src\/Pyz\/Zed\/MerchantProductOfferSearch\/MerchantProductOfferSearchConfig.php` | `MerchantProductOfferSearchConfig::PUBLISH_MERCHANT_PRODUCT_OFFER_QUEUE` |\n| `src\/Pyz\/Zed\/PriceProductMerchantRelationshipStorage\/PriceProductMerchantRelationshipStorageConfig.php` | `PUBLISH_PRICE_PRODUCT_MERCHANT_RELATIONSHIP_QUEUE`, `PUBLISH_PRICE_PRODUCT_CONCRETE_MERCHANT_RELATIONSHIP_QUEUE`, `PUBLISH_PRICE_PRODUCT_ABSTRACT_MERCHANT_RELATIONSHIP_QUEUE` |\n| `src\/Pyz\/Zed\/PriceProductOfferStorage\/PriceProductOfferStorageConfig.php` | `PriceProductOfferStorageConfig::PUBLISH_PRICE_PRODUCT_OFFER_QUEUE` |\n| `src\/Pyz\/Zed\/ProductAlternativeStorage\/ProductAlternativeStorageConfig.php` | `ProductAlternativeStorageConfig::PUBLISH_PRODUCT_ALTERNATIVE_QUEUE` |\n| `src\/Pyz\/Zed\/ProductCategoryFilterStorage\/ProductCategoryFilterStorageConfig.php` | `ProductCategoryFilterStorageConfig::PUBLISH_PRODUCT_CATEGORY_FILTER_QUEUE` |\n| `src\/Pyz\/Zed\/ProductDiscontinuedStorage\/ProductDiscontinuedStorageConfig.php` | `ProductDiscontinuedStorageConfig::PUBLISH_PRODUCT_DISCONTINUED_QUEUE` |\n| `src\/Pyz\/Zed\/ProductGroupStorage\/ProductGroupStorageConfig.php` | `ProductGroupStorageConstants::PUBLISH_PRODUCT_GROUP_QUEUE` |\n| `src\/Pyz\/Zed\/ProductListSearch\/ProductListSearchConfig.php` | `ProductListSearchConfig::PUBLISH_PRODUCT_LIST_SEARCH_QUEUE` |\n| `src\/Pyz\/Zed\/ProductListStorage\/ProductListStorageConfig.php` | `PUBLISH_PRODUCT_LIST_QUEUE`, `PUBLISH_PRODUCT_LIST_PRODUCT_ABSTRACT_QUEUE`, `PUBLISH_PRODUCT_LIST_PRODUCT_CONCRETE_QUEUE` |\n| `src\/Pyz\/Zed\/ProductMeasurementUnitStorage\/ProductMeasurementUnitStorageConfig.php` | `ProductMeasurementUnitStorageConfig::PUBLISH_PRODUCT_MEASUREMENT_UNIT_QUEUE` |\n| `src\/Pyz\/Zed\/ProductOfferAvailabilityStorage\/ProductOfferAvailabilityStorageConfig.php` | `ProductOfferAvailabilityStorageConfig::PUBLISH_PRODUCT_OFFER_AVAILABILITY_QUEUE` |\n| `src\/Pyz\/Zed\/ProductOptionStorage\/ProductOptionStorageConfig.php` | `ProductOptionStorageConfig::PUBLISH_PRODUCT_OPTION_QUEUE` |\n| `src\/Pyz\/Zed\/ProductPackagingUnitStorage\/ProductPackagingUnitStorageConfig.php` | `ProductPackagingUnitStorageConfig::PUBLISH_PRODUCT_PACKAGING_UNIT_QUEUE` |\n| `src\/Pyz\/Zed\/ProductQuantityStorage\/ProductQuantityStorageConfig.php` | `ProductQuantityStorageConfig::PUBLISH_PRODUCT_QUANTITY_QUEUE` |\n| `src\/Pyz\/Zed\/ProductReviewSearch\/ProductReviewSearchConfig.php` | `ProductReviewSearchConfig::PUBLISH_PRODUCT_REVIEW_QUEUE` |\n| `src\/Pyz\/Zed\/ProductReviewStorage\/ProductReviewStorageConfig.php` | `ProductReviewStorageConfig::PUBLISH_PRODUCT_REVIEW_STORAGE_QUEUE` |\n| `src\/Pyz\/Zed\/ProductSearchConfigStorage\/ProductSearchConfigStorageConfig.php` | `ProductSearchConfigStorageConfig::PUBLISH_PRODUCT_SEARCH_CONFIG_QUEUE` |\n| `src\/Pyz\/Zed\/ProductSetPageSearch\/ProductSetPageSearchConfig.php` | `ProductSetPageSearchConfig::PUBLISH_PRODUCT_SET_PAGE_QUEUE` |\n| `src\/Pyz\/Zed\/ProductSetStorage\/ProductSetStorageConfig.php` | `ProductSetStorageConfig::PUBLISH_PRODUCT_SET_QUEUE` |\n| `src\/Pyz\/Zed\/ShoppingListStorage\/ShoppingListStorageConfig.php` | `ShoppingListStorageConfig::PUBLISH_SHOPPING_LIST_QUEUE` |\n| `src\/Pyz\/Zed\/TaxProductStorage\/TaxProductStorageConfig.php` | `TaxProductStorageConfig::PUBLISH_TAX_PRODUCT_QUEUE` |\n\nEach file follows the same pattern:\n\n```php\n\/\/ Before:\nuse Spryker\\Shared\\Publisher\\PublisherConfig;\n\npublic function getQueueName(): string\n{\n return PublisherConfig::PUBLISH_QUEUE;\n}\n\n\/\/ After (example for CategoryImageStorage):\nuse Spryker\\Shared\\CategoryImageStorage\\CategoryImageStorageConfig as SprykerSharedCategoryImageStorageConfig;\n\npublic function getQueueName(): string\n{\n return SprykerSharedCategoryImageStorageConfig::PUBLISH_CATEGORY_IMAGE_QUEUE;\n}\n```\n\n### 4. Create the new queues in the broker\n\nAfter completing all configuration changes, execute the following command to create the new queues in your message broker:\n\n```bash\nvendor\/bin\/console queue:setup\n```\n\n## Related documentation\n\n- [Configure event queues](\/docs\/dg\/dev\/backend-development\/data-manipulation\/event\/configure-event-queues.html)\n- [Optimizing Jenkins execution with the resource-aware queue worker](\/docs\/dg\/dev\/backend-development\/cronjobs\/optimizing-jenkins-execution.html)\n","pubDate":"Fri, 03 Apr 2026 07:55:48 +0000","link":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/split-queues-performance.html","guid":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/split-queues-performance.html"},{"title":"Using the Support Hub","description":"This document describes how to use the support hub to create and manage your tickets.\n\n## Prerequisites\n\n- Log in at the [Spryker Portal](https:\/\/portal.spryker.com). If you don't have access to the Spryker Portal, request it using [this form](https:\/\/portal.spryker.com\/request-access).\n- Go the the Support Hub, using the squares menu in the top right.\n\n## Create a new ticket\n\nTo create a new ticket, click **Create a ticket** and follow the wizard.\n\nWhen creating a ticket, use the recommendations in [Share secrets with the Spryker Support team](\/docs\/about\/all\/support\/share-secrets-with-the-spryker-support-team.html).\n\n\nThe following are the top-level categories of tickets and their description.\n\n### Report a Problem or Incident\n\nProblems can be reports suspecting a bug or issues with the hosting services. To speed up the resolution of such tickets, make sure to follow [Getting the most out of Spryker support](\/docs\/about\/all\/support\/getting-the-most-out-of-spryker-support.html) before you submit your request.\n\n### Ask a Question\n\nFor any questions about Spryker. We want the knowledge about Spryker to be available to everyone. So, we'll provide you with a link to [Spryker Community](https:\/\/commercequest.space\/) to ask your question there. If there are docs on the topic, we will provide a link to that.\n\n### Infrastructure Change Request and Access Management\n\nRequest all currently supported standard changes, such as requesting changes to non-production environments sizing, IAM users and environment provisioning.\n\n### Reporting a Problem with Spryker CI\n\nReport an issue with Spryker CI (Buddy), such as errors or issues with its UI or pipeline runs.\n\n### Announce a Go Live\n\nInform the Customer Success Team about being close to go live.\n\n### Request Help with Spryker ACP\n\nReport an issue with an Spryker ACP connector.\n\n### Request Professional Services\n\nThis category offers a selection of professional services we are offering. For example, you may need it when implementing a complex custom feature.\n\n### Request Help with Spryker Code Upgrader\n\nRequest help with the Upgrader. These requests are processed by our Upgrader experts.\n\n### Announce High Traffic\/Load\n\nLet us know about events or time periods in which you expect a higher than usual load on your production enviornments. We can use this information to check auto scaling settings and evaluate if they need to be adjusted to meet your demands.\n\n### Emergencies\n\nEmergencies are reserved for problems that have significant business impact now or very soon. Emergency tickets regularly start an [escalation](\/docs\/about\/all\/support\/support-case-escalations.html). This category shouldn't be used to speed up requests or problem reports. Emergencies need to be associated with significant risk or business impact, like revenue, security, or go-lives.\n\n### Info on Change Requests\n\n{% info_block warningBox \"Plan your change requests and use the right request form\" %}\n\nBecause of verification processes and role-based access control mechanisms, change requests take some time to process. Expect 3-5 days of processing time.\n\nBecause of contractual reasons, only customers can request new environments or access to environment monitoring, not partners.\n\n{% endinfo_block %}\n\n## Manage tickets\n\nClicking on **View tickets** opens the list of tickets your organisation has opened. To view the details of a particular ticket, click on the \"Details\" button. Here you can take a look at the communication history, view the status of the ticket and associated Jira ticket, and inspect the assigned priority.\n\n### Ticket receipts and notifications\n\nWhen creating a ticket, or when there are meaningful updates to your ticket, like a status change or new comments, you will receive email notifications. Notifications are sent to the email address associated with the Spryker Portal account that was used to create a ticket.\n\nIf you are managing multiple projects or have a high volume of tickets and communication with us, knowing the structure of our notifications and receipts can help you prepare forwarding or labelling rules in your email client:\n\n\n- Ticket confirmation emails are sent when you create a ticket or when its status is updated. Subject pattern:\n\n```bash\nCase Receipt - Case ID: {CASE NUMBER} - Customer: {CUSTOMER NAME} - Status: {STATUS}. {TRACKING ID}\n```\n\n- Change request confirmation emails are sent when you create a change request. Subject pattern:\n\n```bash\nChange Request Receipt - Case ID: {CASE NUMBER} - Customer: {CUSTOMER NAME} - Status: {STATUS}. {TRACKING ID}\n```\n\n- ETA update notification emails are sent when the ETA on your ticket is updated. Subject pattern:\n\n```bash\nCase ETA Update - Case ID: {CASE NUMBER} - Customer: {CUSTOMER NAME}} - ETA: {ETA}. {TRACKING ID}\n```\n\n- Emergency ticket emails are sent when you declare an emergency or your emergency ticket's status is updated. Subject pattern:\n\n```bash\nEmergency {STATUS} - Case ID: {CASE NUMBER} - Customer: {CUSTOMER NAME} {TRACKING ID}\n```\n\n- Ticket comment notification emails are sent when there is a new comment in your ticket. Subject pattern:\n\n```bash\nCase Comment Notification - Case ID: {CASE NUMBER} - Customer: {CUSTOMER NAME} - Status: {STATUS} {Tracking ID}\n```\n","pubDate":"Fri, 03 Apr 2026 07:30:45 +0000","link":"https:\/\/docs.spryker.com\/docs\/about\/all\/support\/using-the-support-portal.html","guid":"https:\/\/docs.spryker.com\/docs\/about\/all\/support\/using-the-support-portal.html"},{"title":"User management (IAM)","description":"The **User management (IAM Users)** panel in [CloudHub](\/docs\/ca\/dev\/cloud-hub\/cloud-hub.html) lets you control infrastructure access and define how team members connect to your environments. You can create, update, and delete IAM users directly through the portal.\n\n## Capabilities\n\n- **Identity provisioning:** Create IAM users for specific environments to ensure precise access control.\n- **Secure connectivity:** Enable or disable VPN access for individual users to secure communications with protected network resources.\n- **Authentication configuration:** Manage SSH public keys for users, enabling secure, key-based authentication for terminal and remote access.\n- **User lifecycle management:** Modify existing user configurations or remove user when it is no longer required.\n\n## Credential delivery for new users\n\nWhen a new IAM user is created, credentials and access configuration are delivered securely across three separate emails:\n\n1. **Password email:** The user's password is delivered via the [OneTimeSecret](https:\/\/onetimesecret.com) service as a one-time link. The link is protected by a passphrase, so the password cannot be accessed without it.\n2. **Passphrase email:** The passphrase required to open the OneTimeSecret link is sent in a separate email. You must have both emails to retrieve the password.\n3. **VPN configuration email:** The VPN configuration file (OVPN profile) required to connect to the protected network is sent in a third separate email.\n\n{% info_block infoBox \"Security note\" %}\n\nKeep all three emails secure. The OneTimeSecret link can only be opened once\u2014if it has already been accessed, request a new user setup through CloudHub.\n\n{% endinfo_block %}\n","pubDate":"Fri, 03 Apr 2026 07:01:37 +0000","link":"https:\/\/docs.spryker.com\/docs\/ca\/dev\/cloud-hub\/user-management.html","guid":"https:\/\/docs.spryker.com\/docs\/ca\/dev\/cloud-hub\/user-management.html"},{"title":"Maintenance","description":"The **Maintenance** panel in [CloudHub](\/docs\/ca\/dev\/cloud-hub\/cloud-hub.html) serves as the communication hub for infrastructure stability and scheduled updates. You will be notified about maintenance operations that are to be executed on your environments. \n\n## Capabilities\n\n- **Operational transparency:** Stay informed about upcoming maintenance windows and infrastructure changes that may affect environment availability.\n- **Proactive planning:** Review scheduled tasks to coordinate deployments and business activities around system updates, minimizing potential downtime.\n- **Reschedule maintenance slot:** Create ticket for our operations team to reschedule maintenance slot.\n","pubDate":"Fri, 03 Apr 2026 06:57:30 +0000","link":"https:\/\/docs.spryker.com\/docs\/ca\/dev\/cloud-hub\/maintenance.html","guid":"https:\/\/docs.spryker.com\/docs\/ca\/dev\/cloud-hub\/maintenance.html"},{"title":"Performance guidelines","description":"These performance guidelines originate from Spryker's years of experience across all kinds of projects, environments, and setups. They cover topics that are often missed at the project level, leading to poor performance or other related issues. The guidelines help you analyze and optimize performance of your website from different perspectives:\n\n- [Keeping dependencies updated](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/keeping-dependencies-updated.html) to maintain optimal performance and security by staying current with Spryker module updates.\n- [Monitoring](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/monitoring.html) to ensure effective application monitoring using APM tools.\n- [General performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/general-performance-guidelines.html) for general approaches to optimizing the server-side execution time.\n- [Architecture performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/architecture-performance-guidelines.html) to optimize performance in the very end servers.\n- [Frontend performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/front-end-performance-guidelines.html) to do the frontend-specific optimization.\n- [Twig performance best practices](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/twig-performance-best-practices.html) to optimize Twig templating engine performance.\n- [Session locks](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/session-locks.html) to optimize session locking mechanisms and reduce performance impact. Also see [Redis session lock](\/docs\/dg\/dev\/troubleshooting\/troubleshooting-performance-issues\/redis-session-lock.html) for troubleshooting session lock issues.\n- [Bot control](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/bot-control.html) to manage honest and malicious bot traffic effectively.\n- [Batch processing of Propel entities](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/performance-guidelines-batch-processing-propel-entities.html) for efficient batch processing, reduced database load, and support for complex entity relationships.\n- [Database performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/database-performance-guidelines.html) to optimize database operations through proper indexing, query optimization, and avoiding common database anti-patterns.\n- [Key-Value storage performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/key-value-storage-performance-guidelines.html) to optimize Redis\/ValKey usage by limiting operations, avoiding admin commands in runtime, and implementing proper caching strategies.\n- [External HTTP requests](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/external-http-requests.html) to understand Spryker's architecture principle of reading from fast storage and learn how to manage external HTTP requests when they're necessary.\n- [Search performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/search-performance-guidelines.html) to optimize Elasticsearch and OpenSearch performance, avoid common search anti-patterns, and implement efficient search queries.\n- [Infrastructure and worker configuration guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/infrastructure-worker-configuration-guidelines.html) to optimize nginx configuration and worker orchestration for multi-store setups.\n- [CDN and traffic management integration](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/cdn-and-traffic-management-integration.html) to configure CDN solutions like Akamai or Cloudflare to work correctly with Spryker's nginx compression and avoid unnecessary data transfer overhead.\n- [Split publish queues for performance](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/split-queues-performance.html) to migrate from a single generic publish queue to dedicated per-module queues for improved throughput, fault isolation, and resource utilization.\n- [Custom code performance guidelines](\/docs\/dg\/dev\/guidelines\/performance-guidelines\/custom-code-performance-guidelines.html) to implement performant custom code including caching strategies, background processing, and Quote calculator optimization.\n- [Common pitfalls in OMS design](\/docs\/pbc\/all\/order-management-system\/latest\/base-shop\/datapayload-conversion\/state-machine\/common-pitfalls-in-oms-design.html) to avoid performance bottlenecks in Order Management System processes, especially ensuring heavy operations run in CLI context rather than during web requests.\n- [Order management system multi-thread](\/docs\/pbc\/all\/order-management-system\/latest\/base-shop\/datapayload-conversion\/state-machine\/order-management-system-multi-thread.html) to process OMS timeouts and conditions in parallel for improved order processing performance.\n- [Troubleshooting performance issues](\/docs\/dg\/dev\/troubleshooting\/troubleshooting-performance-issues\/troubleshooting-performance-issues.html) for detecting and fixing common performance problems.\n- [Order details page performance guidance](\/docs\/pbc\/all\/order-management-system\/latest\/base-shop\/order-management-feature-overview\/order-details-page-performance-overview.html) to optimize the order detail page in the Back Office\n","pubDate":"Fri, 03 Apr 2026 06:54:22 +0000","link":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/performance-guidelines.html","guid":"https:\/\/docs.spryker.com\/docs\/dg\/dev\/guidelines\/performance-guidelines\/performance-guidelines.html"},{"title":"CloudHub","description":"

CloudHub is a centralized self-service portal that lets you manage your Spryker infrastructure directly, without raising manual support requests for routine tasks. It provides a streamlined interface for provisioning resources and managing access.<\/p>\n

Technical teams can use CloudHub to maintain a clear overview of their cloud assets and keep access and storage resources aligned across environments, such as staging and production.<\/p>\n

CloudHub includes the following panels:<\/p>\n