Best Practices
Contents:
- Development Considerations
- Deployment Considerations
- DEP-1: Provision Sufficient Physical Memory
- DEP-2: Make sure that the CPU is not overloaded
- DEP-3: Make sure that the network is not overloaded
- DEP-4: Use a separate back-end subnet for best security
- DEP-5: Use a single network switch for SOSS when possible
- DEP-6: Use a dedicated caching tier with SOSS Remote Client
- DEP-7: Use banks of web farms instead of a large monolithic farm
- DEP-8: Use a VPN for connections over public networks
- DEP-9: If you use NLB, make sure SOSS is on a separate NIC
- DEP-10: Guidelines for sharing sessions in an ASP.NET farm
- DEP-11: Be sure to enable event handling’s configuration parameter
- DEP-12: Configure host gateways when using the ScaleOut Remote Client libraries
- DEP-13: Standalone hosts can use a loopback adapter if a network is not available or to keep hosts from discovering each other
- DEP-14: When running SOSS on VMware guests, follow these guidelines for best performance
- DEP-15: When configuring SOSS with multicast disabled, follow these guidelines
- Management Considerations
- MGT-1: Track memory usage
- MGT-2: Use sequential shut down process
- MGT-3: Avoid SOSS restart as first step in recovery
- MGT-4: Avoid simultaneous management changes on multiple machines
- MGT-5: Avoid dynamically moving virtual servers running SOSS
- MGT-6: Use a rolling upgrade when upgrading minor and hot fix releases
- MGT-7: Follow this process to update a license key for the same major version
- MGT-8: Upgrading a SOSS data grid to Version 5
- Protecting .NET Framework Configuration Sections