Story
Akamai
WrikeHow Wrike Runs Web Performance on App and API Protector
Wrike, an information technology organization in the United States, uses App and API Protector from Akamai to support web performance for platform and web teams.
Wrike standardized edge delivery on Akamai instead of keeping parallel copies.
“Information Technology work at Wrike spans more than one site, even when headquarters sits in the United States.”
“Platform and web teams asked for a shared way to run web performance without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Platform and web teams work from the same App and API Protector record for edge delivery |
| Capability | Edge delivery can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for edge delivery |
Story
Information Technology work at Wrike spans more than one site, even when headquarters sits in the United States. Edge delivery was splitting across regional habits. Platform and web teams asked for a shared way to run web performance without freezing local judgment.
Akamai (App and API Protector) is what they standardized on. Akamai operates a large edge platform for content delivery, application security, and microsegmentation. Wrike uses it as the system of record for edge delivery, with platform and web teams as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
