Delivering Ticketmaster at the edge, at half the cost of legacy CDN
The next generation of the Ticketmaster platform
In order to stay ahead of the competition and create more consistent digital experiences for customers, Ticketmaster focused on improving their user experience by making investments to modernize their tech stack. In 2019, the Ticketmaster team successfully migrated 15+ years of content delivery rules from their legacy CDN provider to Fastly in three months.
Making hard decisions that come with migrating technology
When CDN tech was emerging about 20 years ago, Ticketmaster was an early adopter -- they built upon that legacy technology, which made it challenging to migrate. In 2019, they endeavored to evolve 15+ years of rules, many of which were undocumented. When the team first evaluated Fastly’s edge cloud platform technology, they scoped the migration to take 12 months, since they had 80+ hostnames across 40+ different properties, and supported the needs of 16 different product teams within Ticketmaster.
The Ticketmaster team had been with their legacy CDN provider for so long that talks of migration raised difficult questions, understanding where decisions had been made, such as why certain configurations were implemented. And many of the people who knew the backstory of why or how those decisions were made were long-gone from the company by the time Todd Jimenez led the effort to migrate to Fastly.
Empowered devs drive organic growth in digital transformation
Lift & shift
In 2019, the cost of delivery on their CDN provider was expanding and because their legacy CDN was a black-box that necessitated many professional services hours to configure, update, and manage, it was taking a long time for the team to implement any changes. They needed a simple way to manage CDN for all brands, including recent acquisitions.
Quick rollbacks and instant changes
Ticketmaster needed tech that could reliably support their longstanding delivery needs, but in a way that empowered the developers at Ticketmaster to make changes, rollback quickly, and configure themselves -- they needed more than legacy CDN could offer. The team had made product requests from their legacy CDN that weren’t getting traction, so as contract renewal came up, they began looking elsewhere.
As Ticketmaster evaluated options, the low barrier to entry and flexibility of the modular design with Fastly was key to their successful migration.
Results 4x faster: migrating 20+ years of legacy code in 3 months
The ease of use of the Fastly platform, along with the flexibility and power it provides, allowed the migration to happen much faster than originally planned. With Fastly support and Ticketmaster developers collaborating directly on Slack, any questions were able to be quickly answered, further reducing the migration time. Amazingly, this combined to drive the total migration time from 12 months to actually finishing in 3 months!
After the migration was complete, the team identified a cost savings of 50% vs their legacy CDN. Plus, the developers at Ticketmaster were empowered by the flexibility of Fastly’s platform, so that they could implement changes via the Fastly Dashboard or the Fastly API, instantly, with ease. The huge savings in developer hours for management of their content delivery needs was a benefit instantly visible, that motivated the team to explore moving additional services to the edge.
Lowering friction between developers and the business
Because of its feature-richness and modular design, using Fastly’s edge cloud platform enables Ticketmaster’s content delivery/infrastructure team to support the varied delivery and security needs of 16 different business units, enabling them to choose which technology they want to use. But developers at Ticketmaster say that they choose Fastly because it’s easy to work with and plays well with other technologies in their stack.
One feature commonly used by the different business units is real-time log streaming with Fastly. Because Fastly uses the syslog format, it’s easy for Ticketmaster’s different business units to integrate their logs with tools like Splunk and BigQuery. While that interoperability wasn’t a driving feature, it’s something that all the teams appreciate. And the real-time visibility into logs helps the team keep a laser focus on performance, plus they can get to the bottom of any issues much faster.
Reflecting on the migration, Todd says, “The ability to do things like shared Slack channels with Fastly is a phenomenal one for us from a support perspective. The ability to easily get access to support is frequently a hurdle in many companies. From my perspective that certainly makes my job easier because when folks have questions they can and they know they can pretty trivially reach out and just say, ‘Hey, Fastly, I'm looking at this. What do you think?’ And that type of collaborative conversation occurs on a pretty regular basis.”