Manage your config.
Extend to the edge.
Using Akamai CLI for Property Manager, our forthcoming Terraform and Jenkins integrations, or the Property Manager API (PAPI) directly, you can set up and orchestrate test properties on the Edge in order to test performance changes, or measure performance for new content. Making Akamai Configuration changes inside your CI/CD workflow allows you to integrate Akamai Property Configuration changes into the rest of your deployment lifecycle.
Test property changes before going live to ensure your site always stays up.
Ensure high performance
Observe how new content will perform on staging so you can push high performing content live.
Integreate testing and deployment into the rest of your DevOps or CI/CD workflows.
After deploying a new version of your origin, automate the process of updating your property configs origin behavior to point to it. Again, this can be achieved using Akamai CLI for Property Manager or you can write your own integration using PAPI.
After the update is complete and verified as valid, cache invalidation with FastPurge using Akamai CLI for Purge uses the Akamai Content Control Utility Version 3 (CCUv3) to ensure the latest content is automatically delivered to your users.
Automate how you deploy applications with Akamai to get releases out to customers faster.
Manage your feature or site rollouts with the Phased Release Cloudlet by defining audience segments and gradually migrating them to new versions while ensuring stability. And if there are any issues, you can roll changes back quickly.
Phased releases are useful for two different scenarios.
The first is when you want to gather user feedback on a change from a specific segment of your audience, e.g. typical market demographics.
The second is when you are rolling out code changes with underlying services for which you have no production baseline resource usage. By phasing the release, you can monitor resources and add more should you need them. If things do break, only a segment of your audience is affected. This can be an invaluable technique for ensuring a smooth rollout.
Controlled traffic migration
Gain control over visitor traffic for phased releases to your users/customers. Define audiences, percentage, control stickiness, and failover settings.
Perform canary release of new software or infrastructure in production with automated failover should you encounter challenges or bugs in productions.
Codeless rule creation
Click to configure and activate rules that define audiences and shift visitor traffic without custom code.
Logic at the Edge
Logic offloaded from your infrastructure to the Edge for additional scale and performance.
Shift traffic between varying geographical regions, infrastructure, or providers.
Extendable UI and API
Extend Cloudlets Policy Manager User Interface and API for use by operations teams. Policies activate in seconds.
Using our Visitor Prioritization Cloudlet or our Application Load Balancer Cloudlet, origin failure need not be a catastrophic event. Akamai lets you failover to a holding page (a so-called “waiting room”), secondary origin, static resources, or a maintenance page, so you retain your traffic as you enact recovery procedures.
by keeping users engaged when your application approaches capacity.
with site outage protection during high value, high traffic events.
Preserve scarce application server capacity
for valuable transactions or visitor segments.
Improve user experience
for overflow traffic with a branded waiting room Protect your business from downtime by balancing multiple cloud providers w/ automated failover capabilities.
Maintain consistent session behavior
for your audience, avoiding disruption when outages occur.
When it comes to real-time content, caching is the enemy. However, very often, real-time simply means instant updates to reflect data changes. Before now, to achieve this real-time aspect, you had to forgo the cache and requests would go directly to origin.
With Fast Purge and Hold-Till-Told, you can instruct Akamai to cache content forever, and purge it in under 5 seconds when it updates. Then, by disabling (or minimizing) the downstream cache hold, your end-users will continuously fetch updates from the Edge, rather than origin, knowing that the latest version will be available when updates are made.
You can automate cache purges in response to content updates at origin using your own CMS, so that cache is intelligently purged every time specific content is changed. You can do this using Akamai CLI for Purge, or our Akamai for WordPress plugin.
Cache (almost) Indefinitely
Ensure your critical content is always ready to serve to your customers.
Caching previously uncached content and intreacing TTL lowers infrastructure costs and increases performance.
Ensure that you are always serving fres and relevant content.