AWS Builder Center

DynamoDB Football Data Modeling Challenges - Terms and Conditions

Terms and Conditions for the DynamoDB Football Data Modeling Challenges

DynamoDB Solutions Architect
Looking for support? Email  dynamodb-developer-challenges@amazon.com .
CHALLENGE TERMS AND CONDITIONS:
By registering for the DynamoDB Data Modeling Challenge ("Challenge") on the Amazon Web Services ("AWS") Builder Center, you agree to be bound by these Terms and Conditions. NO PURCHASE NECESSARY. VOID WHERE PROHIBITED.
The Challenge consists of four (4) individual design challenges released on a rolling schedule. Each challenge has a one (1) week submission period during which participants may submit a DynamoDB data model and design document through the AWS Builder Center ("Submission") for a chance to win an AWS-branded jacket (approximate retail value $100 USD).
Challenge
Title
Submission Period
Challenge 1
The Virtual Waiting Room
July 3, 2026 12:00am PT - July 10, 2026 11:59pm PT
Challenge 2
The Fair Seat Purchase
July 17, 2026 12:00am PT - July 31, 2026 11:59pm PT
Challenge 3
The Stadium Concessions Express
July 31, 2026 12:00am PT - August 7 2026 11:59pm PT
Challenge 4
The Infinite Leaderboard
August 14, 2026 12:00am PT - August 21, 2026 11:59pm PT
To qualify for the Challenge, the Submission must include (1) a NoSQL Workbench data model export, (2) a design document explaining all required deliverables, (3) an access pattern matrix, and (4) a comment on the Builder Center challenge page describing something learned while completing the challenge.
Must be at least 18 years of age and have a builder.aws.com profile to be eligible for participation in the Challenge. Excludes individuals living in Argentina, Australia, Brazil, Hong Kong, Italy, Philippines, Poland, Russia, Singapore, Spain, Thailand, Vietnam, Cuba, Iran, Syria, North Korea, and the region of Crimea. AWS, Amazon, employees of AWS, employees of Amazon and their immediate family members and members of their households are not eligible to participate. Limit one entry per person per challenge.

Submission Requirements

To enter, participants must complete the following steps before the applicable deadline:
  • Complete the AWS Pulse survey linked on the Builder Center challenge page. The survey requires: your name, email address, Builder Center alias, and a link to a public GitHub repository containing your submission content.
  • Create a public GitHub repository containing the following deliverables:
#
Deliverable
Format
Description
1
**NoSQL Workbench Data Model**
`.json` export file from NoSQL Workbench
The complete DynamoDB table design exported from [NoSQL Workbench for Amazon DynamoDB](<
 https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/workbench.html> 
). Must include all tables, GSIs, LSIs, key schemas, and sample data items (minimum 5 representative items per table/index).
2
**Design Document**
Markdown (`.md`)
A written explanation covering all required deliverables listed in the challenge description (see challenge-specific criteria below). Must explain *why* each design decision was made, not just *what* was built.
3
**Access Pattern Matrix**
Table in the design document or separate CSV
A matrix mapping every access pattern to the table/index, key condition, and filter expression used to serve it.
  • Post a comment on the Builder Center challenge page describing something you learned while completing the challenge.
The GitHub repository must be public and accessible at the time of judging. Repositories that are private, deleted, or otherwise inaccessible at the time of evaluation will be disqualified.

Evaluation Process

Within two (2) weeks of each challenge's submission deadline, AWS will, in accordance with the judging criteria described below, evaluate all eligible Submissions received during that challenge's Submission Period and select passing entries. Submissions will be evaluated by a combination of AI tools and subject matter experts.

Judging Criteria

All eligible entries received during the applicable Submission Period will be evaluated using a combination of AI tools and human review by AWS subject matter experts. Each submission is evaluated across four scoring categories. Each category is scored Pass / Fail. A submission must achieve Pass in all four categories to be eligible for prizes.

Category 1: Completeness (Pass / Fail gate)

Did the candidate deliver everything the challenge asked for?
Verdict
Criteria
**Pass**
All three required deliverables are present in the linked GitHub repository. The NoSQL Workbench model is a valid, importable `.json` file. The design document addresses every required deliverable bullet in the challenge description. The access pattern matrix covers every pattern referenced in the design. A comment has been posted on the Builder Center challenge page describing something learned.
**Fail**
Any required deliverable is missing from the GitHub repository, the repository is not publicly accessible, the NoSQL Workbench file is corrupt/not importable, the design document skips one or more required deliverable bullets, or the Builder Center comment is absent.
A Fail in Completeness disqualifies the submission from further evaluation.

Category 2: Data Model Correctness

Does the DynamoDB schema actually work for the stated access patterns?
Verdict
Criteria
**Pass**
Every access pattern in the matrix that can most efficiently be served by a Query or GetItem operation uses one. Scans are only used for access patterns where they represent a more efficient design compared to alternatives. Conditional write expressions and transactions are specified where required in the design and are syntactically valid. All DynamoDB service limits, including but not limited to item size limits of 400 KB and partition capacity limits of 1000 WCU / 3000 RCU are respected. Any design accommodations to these limits, such as cross-partition scatter-gather or the use of item collections, must be explicitly stated.
**Fail**
Unnecessary Scan operations are used, a key schema makes a required query impossible, conditional writes or transactions are required but not defined, or DynamoDB service limits would prevent the design from meeting requirements.

Category 3: Scalability, Performance, and Cost Optimization

Will this design hold up at the scale stated in the challenge?
Verdict
Criteria
**Pass**
Proposed design addresses all requirements at the scale specified and respects any design constraints. Future scaling constraints are discussed if they will appear with application growth. Read patterns use eventually-consistent reads where strong consistency isn't required. GSI projections are intentionally scoped. Where multiple data models could address a requirement, the lowest cost model is chosen.
**Fail**
The design has a clear scaling bottleneck, ignores the throughput requirements and constraints of the challenge, or proposes a significantly more expensive design than what is required.

Category 4: Design Rationale & Trade-off Awareness

Does the candidate understand and articulate the trade-offs in their design?
Verdict
Criteria
**Pass**
The design document explains *why* each key schema was chosen. Trade-offs are explicitly called out (e.g., "write sharding improves throughput but requires scatter-gather on reads"). The candidate acknowledges limitations of their approach and describes what they'd do differently if scale requirements changed. Cost implications are discussed where relevant.
**Fail**
No meaningful rationale. The design document provides only schema with no explanation of choices or awareness of trade-offs.

Challenge-Specific Deliverables

The following sections define what judges will verify for each challenge under Category 1 (Completeness). Criteria specify outcomes the model must support - not specific attributes or implementation approaches. The model must provide a means to achieve each outcome; how it does so is the candidate's design choice to make and defend.

Challenge 1 - The Virtual Waiting Room

Deliverable
What Judges Will Verify
**Table design for the waiting room queue**
NoSQL Workbench model provides a means to: (1) uniquely identify each fan in the queue, (2) determine a fan's relative position in the queue, (3) determine when a fan entered the queue, (4) determine whether a fan is currently waiting, eligible to browse, or has already been promoted, and (5) identify which promotion batch a fan belongs to. Key schema must support high-throughput concurrent writes during the initial arrival stampede without creating a single hot partition. Sample data must demonstrate at least 5 fans across multiple queue positions and eligibility states.
**Fair queue position assignment strategy**
Design doc explains the mechanism by which fans receive a deterministic queue position upon arrival. Must address: (1) how relative ordering fairness is established among near-simultaneous arrivals, (2) how the system handles clock skew or timing ambiguity, and (3) why the mechanism is resistant to gaming (a fan cannot manipulate their position by retrying or timing their request).
**Batch promotion strategy**
Design doc describes the mechanism for transitioning fans from "waiting" to "eligible to browse." Must address: (1) how the system determines how many fans to promote in each batch, (2) what event or condition triggers a promotion, and (3) how the system guarantees it does not promote more fans than the downstream purchasing system can absorb.
**Fan status query design**
Design doc and access pattern matrix show how an individual fan can retrieve their current queue status (position, estimated wait, eligibility) via a low-latency read. The approach must remain performant when millions of fans are polling concurrently - the design must not require a Scan on every fan status request.

Challenge 2 - The Fair Seat Purchase

Deliverable
What Judges Will Verify
**Table design for seat inventory and purchase transactions**
NoSQL Workbench model provides a means to: (1) uniquely identify every seat in the venue (by section, row, and seat), (2) determine whether a seat is currently available, held, or sold, (3) determine when a hold expires, (4) identify who holds or owns a seat, and (5) track the purchase transaction lifecycle (payment status, confirmation). Key schema must support concurrent seat lookups and atomic status transitions. Sample data must demonstrate seats in each state (available, held, sold).
**Seat reservation strategy**
Design doc explains how the system guarantees that a seat cannot be sold to two fans simultaneously. Must describe: (1) the atomic mechanism (conditional writes, transactions, or equivalent) that transitions a seat from available to held, (2) how concurrent attempts on the same seat are handled (exactly one succeeds, others receive a defined failure), and (3) how the held-to-sold transition is similarly protected.
**Temporary hold with automatic expiration**
Design doc describes: (1) the mechanism by which holds expire after a defined window, (2) how expired holds make seats available again to other fans, and (3) whether the release is immediate (active) or eventually consistent (passive/TTL-based) and the trade-offs of that choice.
**Architecture diagram of the purchasing flow**
A visual or structured representation showing the full lifecycle: browse available seats → select seat → seat held atomically → payment processed → seat confirmed or released on timeout. The diagram must show where DynamoDB operations occur in the flow.

Challenge 3 - The Stadium Concessions Express

Deliverable
What Judges Will Verify
**Table/index design for fans, orders, and concession stands**
NoSQL Workbench model provides a means to: (1) represent fans and their seating locations, (2) represent orders with their contents, placement time, fulfillment status, and assigned stand, and (3) represent concession stands and their locations. Key schema must support both high-throughput order ingestion during the halftime surge AND efficient queries for unfulfilled orders. Sample data must demonstrate orders in multiple states (pending, in-progress, fulfilled) across multiple stands.
**Pending orders sorted by longest wait time**
Design doc explains the index strategy that enables querying pending orders in wait-time order. Must acknowledge that DynamoDB does not support global cross-partition sorting and describe how the design addresses this constraint.
**Order-to-stand proximity assignment**
Design doc describes: (1) how seat-to-stand proximity is represented in the data model, (2) how the system determines which stand should fulfill a given order, and (3) whether assignment happens at write time or query time, and the trade-offs of that choice.

Challenge 4 - The Infinite Leaderboard

Deliverable
What Judges Will Verify
**Table design for leaderboards, scores, and participants**
NoSQL Workbench model provides a means to: (1) create and identify arbitrary named leaderboards, (2) record a participant's score on a given leaderboard, (3) query top-N participants on a given leaderboard, and (4) query all leaderboards a given participant is active on. Sample data must demonstrate at least two leaderboards with multiple participants at varying scores.
**Partition key strategy for high-velocity writes**
Design doc explains how writes are distributed to avoid hot partitions when a single leaderboard receives >1,000 writes/second. Must explicitly acknowledge the read-side trade-off introduced by any write-distribution strategy.
**Core access pattern strategies**
Design doc describes the mechanism for serving each of the four required access patterns: (1) top-N scores on a given leaderboard, (2) a specific participant's rank and score on a given leaderboard, (3) neighboring records around a participant's position, and (4) all leaderboards a participant is active on with their scores. For each pattern, must identify which table/index is used and the key condition that serves it.

Prizes

Approximate retail value of the prizes are described below:
The first 50 entries per challenge that achieve a Pass in all four judging categories are eligible for a prize consisting of an AWS-branded jacket (approximate retail value $100 USD). Prizes are awarded in the order in which qualifying submissions were received. A participant may receive a prize from at most one challenge across the series - subsequent qualifying entries from the same participant will not be awarded.
If you are selected as a winner, AWS will contact you using the email address you submit to enter the Challenge. The prize will be shipped within 60 days of winner announcement. Failure to provide the requested information or to respond to communications about the Challenge within a reasonable period of time, as determined by AWS in its sole discretion, may result in the forfeiture of the prize.

Additional Terms

Entries that do not meet the requirements set forth in these Terms and Conditions may be disqualified in AWS's sole discretion.
By accepting the prize, you confirm that your receipt is neither prohibited nor inconsistent with any applicable laws, regulations, or binding orders, including applicable ethics or procurement rules, your receipt will not create a conflict of interest for AWS, and there are no ongoing competitive procurements for which your receipt of this benefit could conflict with AWS's participation in the competition.
The following personal information will be collected by AWS for the Challenge solely for the purposes of administering the Challenge and verifying participant eligibility: name, email address, and to the extent you are a winner, mailing address. Failure to provide all necessary personal information may result in participants' participation in the Challenge being deemed ineligible. AWS handles your information in accordance with the  AWS Privacy Notice  (< https://aws.amazon.com/privacy/> ).
A winners list will be available at builder.aws.com for up to a year after the date on which the article announcing the winners is published to the AWS Builder Center. Acceptance of prize by the winner constitutes permission for AWS to use winners' names or likenesses, and city, state or province, and country, if submitted to AWS, for any disclosures required by law, including a winners list, and for advertising and promotional purposes relating to the Challenge in any and all media now or hereafter devised, worldwide in perpetuity (or to the maximum extent permissible under applicable law), without additional compensation, notification or permission, unless prohibited by law.
By submitting your submission to the Challenge, you represent and warrant that your submission does not: (i) perform or promote activities that are illegal; (ii) violate or infringe the intellectual property, proprietary, or other rights of others; (iii) perform or promote activities that are offensive or disparaging in any manner; or (iv) cause harm to others or to AWS's operations or reputation.
The Challenge is sponsored by AWS. AWS reserves the right to cancel or modify the Challenge at any time and for any reason. AWS and its affiliates and licensors will not be liable to you under any cause of action or theory of liability relating to the Challenge, even if a party has been advised of the possibility of such damages, for (a) indirect, incidental, special, consequential, or exemplary damages, or (b) lost profits, revenues, customers, opportunities, or goodwill. In any case, AWS and its affiliates' and licensors' aggregate liability under these Terms and Conditions will not exceed USD $100. The limitations in this paragraph shall apply only to the maximum extent permitted by applicable law.

TAX OBLIGATIONS

Winners are responsible for all federal, state, local, and foreign taxes associated with accepting and using a prize. Amazon may withhold taxes from prize payments where required by law. Before receiving any cash prize, winners must provide all requested tax documentation (including IRS Form W-9 for U.S. persons or the appropriate IRS Form W-8 series for non-U.S. persons) to Amazon's prize administrator. Cash prizes may be subject to tax reporting, including on IRS Forms 1099 or 1042-S. All prize amounts are stated as gross amounts before any applicable tax withholding, and winners will receive the net amount after withholding (if any).
For physical prizes, winners are responsible for any import duties, taxes, or customs fees required by their jurisdiction. Amazon's fulfillment partners may facilitate delivery but do not assume responsibility for such charges.
Winners should consult their own tax advisors regarding the tax consequences of accepting a prize in their jurisdiction.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article