Skip to content

Commit

Permalink
Fixed Redirect
Browse files Browse the repository at this point in the history
  • Loading branch information
@simonbrugger
simonbrugger committed Nov 15, 2023
1 parent 6c4b39a commit 43f3ff4
Showing 1 changed file with 46 additions and 45 deletions.
91 changes: 46 additions & 45 deletions docs/ca/dev/multi-store-setups/multistore-setup-options.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ description: Learn about all the setup options you have for a multi-store enviro
template: howto-guide-template
redirect_from:
- /docs/cloud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.html
- /docs/scos/user/introduction-to-the-spryker-commerce-os/multiple-stores/multi-store-setup.html
related:
- title: Add and remove databases of stores
link: docs/cloud/dev/spryker-cloud-commerce-os/multi-store-setups/add-and-remove-databases-of-stores.html
Expand Down Expand Up @@ -85,13 +86,13 @@ The following table provides details on infrastructure for this setup:

<div class="width-100">

| What | How |
|------|-----|
| DB | Shared |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared |
| Spryker Storefront Yves |Shared |
| Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office) | Shared |
| Complexity of rollout | Low |
| What | How |
| ------------------------------------------------------------------------------ | ------ |
| DB | Shared |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared |
| Spryker Storefront Yves | Shared |
| Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office) | Shared |
| Complexity of rollout | Low |

</div>

Expand Down Expand Up @@ -129,13 +130,13 @@ The following table provides details on the infrastructure for this setup:

<div class="width-100">

| What | How |
|------|-----|
| DB | Separate |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared |
| Spryker Storefront Yves |Shared |
| What | How |
| ------------------------------------------------------------------------------ | -------- |
| DB | Separate |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared |
| Spryker Storefront Yves | Shared |
| Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office) | Shared |
| Complexity of rollout | Medium |
| Complexity of rollout | Medium |

</div>

Expand Down Expand Up @@ -183,13 +184,13 @@ The following table provides details on the infrastructure for this setup:

<div class="width-100">

| What | How |
|------|-----|
| DB | Separate |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Separate |
| Spryker Storefront Yves |Separate |
| Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office) | Separate |
| Complexity of rollout | High |
| What | How |
| ------------------------------------------------------------------------------ | -------- |
| DB | Separate |
| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Separate |
| Spryker Storefront Yves | Separate |
| Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office) | Separate |
| Complexity of rollout | High |

</div>

Expand All @@ -199,35 +200,35 @@ The following tables contain high-level criteria that sum up the setups describe

**Infrastructure details:**

| What | Setup 1 | Setup 2 | Setup 3 |
|------------------------------------------------------------------------|---------|----------|----------|
| DB | Shared | Separate | Separate |
| What | Setup 1 | Setup 2 | Setup 3 |
| ----------------------------------------------------------------------------- | ------- | -------- | -------- |
| DB | Shared | Separate | Separate |
| Ke-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared | Shared | Separate |
| Spryker Storefront Yves | Shared | Shared | Separate |
| Spryker Commerce OS | Shared | Shared | Separate |
| Complexity of rollout | Low | Medium | High |
| Spryker Storefront Yves | Shared | Shared | Separate |
| Spryker Commerce OS | Shared | Shared | Separate |
| Complexity of rollout | Low | Medium | High |

**High-level characteristics:**

| What | Setup 1 | Setup 2 | Setup 3 |
|-------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
| Stores | 1 store or multiple stores | Multiple stores | Multiple stores |
| ES and Redis | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) |
| Database | One shared database | Virtual separated database per store: you can have cluster sharing same or use different database setups | Separate database per store |
| What | Setup 1 | Setup 2 | Setup 3 |
| ------------------------------------ | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Stores | 1 store or multiple stores | Multiple stores | Multiple stores |
| ES and Redis | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) | Each store has a dedicated index for ES and its own key-value storage namespace (Redis) |
| Database | One shared database | Virtual separated database per store: you can have cluster sharing same or use different database setups | Separate database per store |
| AWS regions | One region with multiple stores | One region with multiple stores | Allows different regions |
| Codebase | Shared codebase | Shared codebase | Shared or separate codebases (up to a project development team) |
| Code bucket/themes | Supported | Supported | Supported (for shared codebase) |
| Centralized third-party integrations | Supported | Supported | Supported (for shared codebase) |
| Fully independent development teams | Not supported | Not supported | Supported (for separate codebases) |
| Codebase | Shared codebase | Shared codebase | Shared or separate codebases (up to a project development team) |
| Code bucket/themes | Supported | Supported | Supported (for shared codebase) |
| Centralized third-party integrations | Supported | Supported | Supported (for shared codebase) |
| Fully independent development teams | Not supported | Not supported | Supported (for separate codebases) |


**Load criteria:**

| | Page view load (Storefront Yves) | Backend load (Spryker Commerce OS) |Database Throughput |Shared data (customers, orders, etc.)|
|------|---|---|---|---|
| SETUP 1 |Normal | Normal |Normal |Yes |
| SETUP 2 | Normal/High | Normal/High | Normal/High | No |
| SETUP 3 | High | High |High |No |
| | Page view load (Storefront Yves) | Backend load (Spryker Commerce OS) | Database Throughput | Shared data (customers, orders, etc.) |
| ------- | -------------------------------- | ---------------------------------- | ------------------- | ------------------------------------- |
| SETUP 1 | Normal | Normal | Normal | Yes |
| SETUP 2 | Normal/High | Normal/High | Normal/High | No |
| SETUP 3 | High | High | High | No |


{% info_block warningBox "High load" %}
Expand All @@ -238,11 +239,11 @@ If you anticipate a high load, it's essential to consult and obtain guidance fro

**Limitations:**

| | Setup 1 | Setup 2 | Setup 3 |
|------|---|---|---|
| ACCESSIBILITY | <ul><li>Data is separated only on the application level.</li><li>Complexity in data separation in the Back Office.</li></ul> | Full data separation | Full data separation |
| MAINTAINABILITY |<ul><li>Not all features fully support Multi-Store in one database. Some features have to be customized as multi-country</li><li>New codebase is rolled out to all countries at once.</li></ul> |<ul><li>Import of each country’s data into its own database only, so there is no shared catalog data.</li> <li>New codebase is rolled out to all countries at once.</li></ul> |<ul><li>Data import has to be executed on all environments.</li><li>It is impossible to roll out the codebase to all regions at the same time.</li></ul> |
| PERFORMANCE |Infrastructure is subject to more frequent scaling up in case of higher loads. | Infrastructure is subject to more frequent scaling up in case of higher loads. |Isolated AWS accounts. |
| | Setup 1 | Setup 2 | Setup 3 |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ACCESSIBILITY | <ul><li>Data is separated only on the application level.</li><li>Complexity in data separation in the Back Office.</li></ul> | Full data separation | Full data separation |
| MAINTAINABILITY | <ul><li>Not all features fully support Multi-Store in one database. Some features have to be customized as multi-country</li><li>New codebase is rolled out to all countries at once.</li></ul> | <ul><li>Import of each country’s data into its own database only, so there is no shared catalog data.</li> <li>New codebase is rolled out to all countries at once.</li></ul> | <ul><li>Data import has to be executed on all environments.</li><li>It is impossible to roll out the codebase to all regions at the same time.</li></ul> |
| PERFORMANCE | Infrastructure is subject to more frequent scaling up in case of higher loads. | Infrastructure is subject to more frequent scaling up in case of higher loads. | Isolated AWS accounts. |

## Next steps

Expand Down

0 comments on commit 43f3ff4

Please sign in to comment.