Story
Akamai
Six FlagsSix Flags Adopts Akamai for Application Delivery
Six Flags, a consumer discretionary organization in the United States, uses Ion from Akamai to support application delivery for network and app owners.
Ion became the place Six Flags uses to steer and protect application traffic as it enters the environment.
“Inside Six Flags, application delivery used to depend on whoever still had the latest file.”
“Network and app owners needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because application traffic has a clear owner |
| Productivity | Handoffs in application delivery sit in a shared queue instead of a mailbox trail |
| Capability | New joiners can see how application delivery actually runs |
Story
Inside Six Flags, application delivery used to depend on whoever still had the latest file. That pattern is common in consumer discretionary groups working out of the United States. Network and app owners needed a system that would still make sense after the original project team moved on.
Six Flags uses Ion from Akamai as the working layer for application traffic. Akamai operates a large edge platform for content delivery, application security, and microsegmentation. The practical change is simple: application delivery has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Six Flags gets from Akamai is a durable place to run application delivery and a way for network and app owners to see the same application traffic at the same time.
