Resource tiers let you select between different sets of resource consumption limits for your EdgeWorkers functions.
There are currently two resource tiers available, Dynamic Compute and Basic Compute. You can choose one of these resource tiers when you Create an EdgeWorker ID.
By default, all EdgeWorker IDs created before resource tiers were introduced execute using the Dynamic Compute resource tier. The limitations applied by this resource tier are the same as when the EdgeWorker ID was created.
You can, however, change an EdgeWorkers function to Basic Compute, a less costly tier with lower limits. For instructions on how to change the resource tier assigned to an EdgeWorkers function see Clone an EdgeWorker ID. The billing rate for each of these resource tiers is different. For information about billing you can contact your Akamai account representative.
See the Resource tier limitations section to review the consumption limits for each resource tier. Review the table below for the supported use cases for each resource tier. Dynamic Compute allows you to implement any currently available EdgeWorkers use case.
|Use Case||Basic Compute||Dynamic Compute|
|Cache Key Manipulation||✓||✓|
|Forwarding / Conditionally Route Traffic||✓||✓|
|Simple regex / hashing / crypto||✓||✓|
|Fetches that GET JSON data and enable personalization||✓||✓|
|Data POSTing for metrics beaconing and error logging||✓||✓|
|Response Body modification||✓|
|Integration with EdgeKV||✓||✓|
|Complex crypto during the responseProvider event handler||✓|
Familiarize yourself with these common terms associated with EdgeWorkers resource tiers and billing.
Contact your Akamai account representative for complete details related to billing.
|Resource tier||A resource tier is a collection of consumption limits for your EdgeWorkers functions. There are currently two resource tiers available, Dynamic Compute and Basic Compute. You can select a resource tier when you Create an EdgeWorker ID.|
|Compute resources||EdgeWorkers compute resources include CPU time, memory usage, and wall time. For a complete list go to the Resource tier limitations section.|
|Traffic hits||Traffic hits are the end user requests made to edge servers on the Akamai Intelligent Edge Platform. For each enabled EdgeWorkers function up to four events can occur. Keep in mind that hits don't always equal events.|
|Million events invoked||Million events invoked is the billing unit of measurement for EdgeWorkers. To calculate your bill we sum up the number of times each event was executed for your traffic over the course of a month. You can configure the events you need to support your business logic. Typically only one or two events per end user request occur for many of the early adopter use cases.|
Updated 10 months ago