Best practices and use case-based provisioning

Every OD property automatically includes a set of “best practices” behaviors in the Default Rule that have been optimized for best performance. You can also apply "use case-based" provisioning to further optimize a configuration based on your specific use case.

Best practices in the Default Rule

Every OD property automatically includes a set of “best practices” behaviors in the Default Rule that have been optimized for best performance. They're included in the background—you don't see them as an actual behavior in the rule. For OD, this includes these behaviors:

  • Allow All Methods on Parent Servers
  • Cache HTTP Error Response
  • Cache HTTP Redirects
  • Caching
  • LDS (Log Delivery Service)
  • Remove Vary Header
  • Tiered Distribution

So, you no longer need to add these individual behaviors and configure them for best results. There are a few points to consider with these behaviors:

  • These behaviors can be overridden as an optional behavior. You can optionally add them to the Default Rule as separate behaviors to have them override these best practices settings. If you add one of these behaviors, you'll see a warning message. This is informational, only.
  • Some best practices behaviors are internal, only. Some behaviors are specific to core platform features for OD or other operations, and you won't see them in the Property Manager catalog. They're enabled by default to improve delivery performance. If you need to provide custom settings, you may be able to apply them in an advanced rule. Talk to your account representative for details.
  • Advanced rules override best practices. If your account representative internally adds a behavior in an advanced rule that conflicts with what an established best practice, the advanced rule settings override the best practices settings.

Mandatory behaviors are used to employ use case-based provisioning

Every new OD configuration includes three mandatory behaviors in the Default Rule—Origin Characteristics, Content Characteristics, and Client Characteristics. These let you provide information about your specific use case for the OD property, and they let you apply optimizations, based on how the configuration is used.

For example, if you're using a custom origin for your content, you can provide your specific Origin Location use case information via the mandatory Origin Characteristics behavior in the Default Rule. OD uses this information to create an appropriate Tiered Distribution hierarchy to improve offload.

Note: If you're not sure what to enter, leave these fields set to Unknown. Use case-based provisioning optimizations will not be applied.

Use case-based provisioning is recommended, but customization is still available

We recommend that you configure the mandatory behaviors to meet your specific use case, and let Akamai optimize the network for your OD property. However, if you want to deploy custom settings, then the behaviors you (or your account representative) add take precedence over the settings used by use case-based provisioning.

For example, if you manually add the Tiered Distribution behavior to your Default Rule, what you've set there will take precedence over the use case-based optimizations that are automatically included when you define your specific Origin Location in the Origin Characteristics behavior.

We also offer mixed mode configuration

Using use case-based behaviors in the Default Rule applies their optimizations to all requests managed by this OD property. This is because the Default Rule applies to all requests.

However, what if you want to apply different optimizations settings for different requests? To do this, you can use Mixed Mode Configuration for OD. This lets you add these use case-based behaviors in other rules outside of the Default Rule. This way, you can set unique match criteria for a request and apply different optimizations for those requests. This is fully discussed in Mixed Mode Configuration for OD.