loadbalancing

Author: sofietoft

13/umbraco-ums/getting-started/for-developers/infrastructure-sizing.md

@@ -1,27 +1,30 @@
-# **Infrastructure sizing**
+# Infrastructure sizing
 
-To determine the optimal infrastructure sizing the most important metric is the number of page views you will need to process. Also peak load is an important factor.
+To determine the optimal infrastructure sizing the most important metric is the number of page views you need to process. Peak load is also an important factor.
 
-uMarketingSuite recommends the following (database) infrastructure sizes when using the following environments.
+The following presents recommendations based on environment as well as the number of expected page views.
 
-**Non-cloud**
+## Non-cloud
 
 - **100.000 page views per month or less:** Database: CPU 2, 4-8 GB RAM, 50GB disk
 - **500.000 page views per month or less:** Database: CPU 4, 8-16 GB RAM, 100GB SSD disk
 - **1.000.000 page views per month or less:** Database: CPU 8, 16-32 GB RAM, 250GB SSD disk
 - **1.000.000 page views per month or more:** Please [contact our Expert Services](mailto:[email protected]) team to discuss the infrastructure requirements.
 
-**Cloud environments (Microsoft Azure, Amazon AWS)**
+## Cloud environments
 
-Because of the rapidly changing naming and sizing of Azure and AWS instances we recommend to use the appropriate supplier tools to determine the exact sizing based on the above non-cloud recommendations.  
-In general for Azure SQL use at least a S3 instance for production purposes.
+Due to the rapidly changing naming and sizing of Azure instances we recommend using the appropriate supplier tools to determine the exact sizing. Base the exact sizing on the non-cloud recommendations above.  
 
-**Umbraco Cloud**
+In general, for Azure SQL use at least a S3 instance for production purposes.
+
+## Umbraco Cloud
 
 - **100.000 page views per month or less:** Standard / Professional
 - **500.000 page views per month or less:** Professional
 - **500.000 page views per month or more:** Professional / Enterprise
 
-Always discuss the exact requirements with your agency and/or the Umbraco Cloud team and if needed discuss Prioritized Cloud Computing, Prioritized Database Performance and/or Dedicated Resources based on the expected load.
+Always discuss the exact requirements with your agency or the Umbraco Cloud team. If needed discuss Prioritized Cloud Computing, Prioritized Database Performance and Dedicated Resources based on the expected load.
 
-*Note: above you will find general recommendations which infrastructure parameters to use. While these should work well for most cases, you may need to adjust the infrastructure parameters to suit your page view processing workload. Very large or heavily trafficked websites may have significantly higher requirements. If you expect high page view peaks it is recommended to scale to a tier higher then normally.*
+{% hint style="info" %}
+Above you will find general recommendations on which infrastructure parameters to use. While these should work well for most cases, you may need to adjust the infrastructure parameters to suit your page view processing workload. Large or heavily trafficked websites may have higher requirements. If you expect high page view peaks it is recommended to scale to a tier higher then normally.
+{% endhint %}

13/umbraco-ums/getting-started/for-developers/loadbalancing-and-cm-cd-environments.md

@@ -1,38 +1,50 @@
+---
+description: Recommendations for using uMS within a load-balanced setup.
+---
+
 # Load balancing and CM/CD Environments
 
-## **Umbraco setup**
+## Umbraco setup
+
+Make sure your Umbraco is setup according to best-practices. Please refer to the [Umbraco documentation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing) for more details.
+
+## Cockpit
+
+For the Cockpit to function properly it is necessary that the cockpit can read the Umbraco login cookie. Umbraco and the site should run on the same domain or sub-domain.
 
-Make sure your Umbraco is setup according to the Umbraco best-practices. Please refer to the [Umbraco documentation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing).
+For example:
 
-## **Cockpit** 
+**Umbraco:** `umbraco.domain.com`  
+**Site:** `domain.com`
 
-**Configuring the AuthCookieDomain cookie**For the cockpit to function properly it is necessary that the cockpit can read the Umbraco login cookie or else the cockpit won't be visible. **Umbraco and the site should run on the same domain / sub-domain**. For example:
+Make sure the AuthCookieDomain in your SecuritySettings of your Umbraco config has the following value:
 
-**Umbraco:** umbraco.domain.com  
-**Site:** domain.com
+```json
+"AuthCookieDomain": ".domain.com",
+```
 
-Make sure the AuthCookieDomain in your SecuritySettings of your Umbraco config is set to
+To learn more, read the documentation about the [SecuritySettings](https://docs.umbraco.com/umbraco-cms/reference/configuration/securitysettings)
 
-    "AuthCookieDomain": ".domain.com",
+## Machine key and Data Protection
 
-Also see: [https://docs.umbraco.com/umbraco-cms/reference/configuration/securitysettings](https://docs.umbraco.com/umbraco-cms/reference/configuration/securitysettings)
+You need to configure machine keys and data protection to **use the same keys on all servers** (content delivery and content-management).
 
-**Machine key / Data Protection**
+Without this setup, each server will generate its own key. This will results in the Umbraco authentication cookie being encrypted and decrypted using different keys leaving the Cockpit unusable on the frontend servers.
 
-You need to configure machine keys / data protection to **use the same keys on all servers** (content delivery and content-management). Without this setup, each server will generate its own key, resulting in that the Umbraco authentication cookie is encrypted and decrypted using different keys and the uMarketingSuite cockpit will not be shown on the front-end servers.
+To learn more, read the [Load Balancing article](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing) in the Umbraco CMS documentation.
 
-Also see the Data Protection section at: [https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing)
+## Bot detection (ping)
 
-## **Bot detection (ping)**
+uMS will perform a ping (POST) to detect if the [visitor is a visitor or a bot](/analytics/types-of-clients/). The `umbraco/umarketingsuite/pagedata/ping` URL should be accessible from the content delivery and front-end servers. Make sure no firewall or other mechanism is blocking POST requests to `umbraco/umarketingsuite/pagedata/ping`. If this URL is blocked, all visitors will be treated like a bot and no analytics data is collected.
 
-uMarketingSuite will perform a ping (POST) to detect if the [visitor is a visitor or a bot](/analytics/types-of-clients/). The url umbraco/umarketingsuite/pagedata/ping should be accessible from the content delivery / front-end servers so make sure no firewall or other mechanism is blocking POST requests to **umbraco/umarketingsuite/pagedata/ping** or else all visitors will be treated like a bot and no analytics data is collected.
+## Configuration
 
-## **Configuration**
+Make sure the `IsProcessingServer` is set to `true` on the content management (Umbraco) environment and to `false` on the content delivery or front-end servers. 
 
-Make sure the **IsProcessingServer** is set to **True** on the content management (Umbraco) server/environment and to **False** on the content delivery / front-end servers in your **uMarketingSuite.config** ([uMarktingSuite v1.x](/installing-umarketingsuite/configuration-options-1-x/)) or **AppSettings.json** ([uMarketingSuite v2.x](/installing-umarketingsuite/configuration-options-2-x/)) file.
+The setting can be found in your `uMarketingSuite.config` ([uMarktingSuite v1.x](/installing-umarketingsuite/configuration-options-1-x/)) or `AppSettings.json` ([uMarketingSuite v2.x](/installing-umarketingsuite/configuration-options-2-x/)) file.
 
-## **Sticky sessions**
+## Sticky sessions
 
-Sticky sessions, also known as session affinity, are essential for the proper functioning of uMarketingSuite in a load-balanced environment. Sticky sessions can be enabled using various methods such as cookie-based, IP-based, or URL-based session affinity, depending on the load balancer configuration. By enabling sticky sessions, you can ensure that user sessions remain intact and data consistency is maintained across the uMarketingSuite application so analytics, a/b testing and personalization can work properly.
+Sticky sessions, also known as session affinity, are essential for the proper functioning of uMS in a load-balanced environment. Sticky sessions can be enabled using different methods such as cookie-based, IP-based, or URL-based session affinity, depending on the load balancer configuration. By enabling sticky sessions, you can ensure that user sessions remain intact and data consistency is maintained across the uMarketingSuite application. Sticky sessions will ensure that analytics, A/B testing and personalization works properly.
 
-Please refer to the documentation or configuration settings of your load balancer for specific instructions on enabling sticky sessions.
+Please refer to the documentation or configuration settings of your load balancer for specific instructions on enabling sticky sessions.