AWS Media and Entertainment United States

PGA TOUR

Real-time Analytics

The PGA TOUR wanted to give fans real-time insight into tournament outcomes, but doing so required a machine learning model that could run thousands of simulations and process nearly four billion records fast enough for live event coverage.

process nearly four billion records
run thousands of simulations

Reported impact

Business outcome

The PGA TOUR can run its model quickly, scale week to week as event complexity changes, and give audiences real-time win and cut probability insights without taking on the operational overhead of managing infrastructure.

  • Customer Experience
  • Scalability

Solution

The PGA TOUR built its Win, Cut Probability model on AWS to calculate a player’s chances of advancing in and winning a tournament while tournaments are in progress. The solution uses Amazon Elastic Container Service (Amazon ECS) with AWS Fargate to run thousands of simulations without managing infrastructure, then relies on Amazon Redshift and Amazon DynamoDB to support analytical and low-latency application workloads behind the fan experience. This serverless architecture lets the PGA TOUR scale week to week as tournament complexity changes, keep operations lean, and deliver immersive probability insights across multiple viewing platforms.

Data flow

Tournament and player data feeds the Win, Cut Probability model, which runs thousands of simulations on Amazon ECS with AWS Fargate and serves analytical outputs backed by Amazon Redshift and Amazon DynamoDB across PGA TOUR viewing experiences.

Solution architecture

4 components · 2 layers
  1. Compute
    • Amazon ECS Runs containerized application workloads and batch simulations.
    • AWS Fargate Provides serverless compute capacity for containerized workloads.
  2. Storage
    • Amazon Redshift Stores analytical datasets and serves aggregated reporting workloads.
    • Amazon DynamoDB Stores low-latency application, search, or telemetry state data.

Architecture clues

  • AWS Serverless helps us scale reliably week to week as we move from event to event.
  • Powered by AWS, advanced data analytics, cloud infrastructure, and serverless services, the Win, Cut Probability model measures a player’s chances of advancing in and winning a tournament.
  • Using Amazon Elastic Container Service (ECS) with AWS Fargate to run thousands of simulations and process nearly four billion records.

Evidence from the source

AWS Serverless helps us scale reliably week to week as we move from event to event.
Amazon DynamoDB is a fully managed, serverless, key-value NoSQL database designed to run high-performance applications at any scale.
Each event brings its own set of complexities from size and scale, and what we need to do.
The PGA TOUR introduced Win, Cut Probability, a novel ML-powered analytics model that provides real-time insights into the likelihood of outcomes during tournaments.
Using Amazon Elastic Container Service (ECS) with AWS Fargate to run thousands of simulations and process nearly four billion records, the PGA TOUR can take advantage AWS’s elasticity, run their model quickly and scale as needed, while offloading the operational overhead of infrastructure management to AWS.
Transparency Evidence & methodology 70/100 reference value · 85% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value70/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    PGA TOUR customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/pga-tour-ecs-case-study/
    Source type
    Vendor-published customer story
    Published
    Jul 1, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.