What is "Use Case-based" provisioning?

Use Case-based provisioning allows you to further optimize a configuration based on your specific use case.

This is accomplished through the implementation of Mandatory Behaviors in the Default Rule, that you use to apply additional, specific settings. Use case-based provisioning has the following characteristics:

  • Mandatory behaviors for use case-based provisioning: Every new AMD configuration includes these behaviors in the Default Rule—Origin Characteristics, Content Characteristics,, Client Characteristics, and Segmented Media Delivery Mode. These let you provide information about your specific use case for the AMD property, and allow you to apply optimizations, based on how the configuration is used. For example:
    • If you're using a custom origin for your content (you are not using NetStorage) you can provide your specific Origin Location use case information. Then, AMD creates an appropriate Tiered Distribution hierarchy to improve offload.
    • You can provide specific Segment Duration use case information for your media. AMD then assigns the appropriate caching settings to improve offload, while maintaining smooth playback.
    Note: If you are unsure of what to enter, leave these fields set to Unknown, and 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 Use Case-based provisioning options and let AMD optimize the network for your AMD property. However, if you want to deploy custom settings, then the behaviors you (or your Account Representative) configure take precedence over the settings used by Use Case-based provisioning. For example:
    • If Use Case-based provisioning is optimizing your caching settings, based on specific use case information you have provided, and you also add and configure the Caching behavior using the Property Manager catalog, then what you have set in the Caching behavior will take precedence.
    • If Use Case-based provisioning is optimizing your Tiered Distribution settings, based on the use case information you have provided, and your Account Representative also configures a custom Tiered Distribution setting, then the latter setting will take precedence.

We also offer use case-based edge maps and mixed mode configuration

Using these behaviors in the Default Rule to apply use case-based provisioning applies their optimizations to all requests managed by this AMD property. This is because the Default Rule applies to all requests, and by default, these behaviors are only available for use in the Default Rule.

However, what if you want to apply different optimizations settings for different requests? We also offer additional functionality to support this:

  • Mixed Mode Configuration for AMD. 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 the document, Mixed Mode Configuration for AMD.
  • Use case-based edge mapping. This lets you specify the delivery mode of content—live vs. on demand—when setting up a property hostname to edge hostname association in your AMD property. By selecting a mode, requests that resolve to the edge hostname are routed to the best Akamai edge map in order to optimize delivery. Details are discussed in How to add Use Case-based Edge Mapping.