Menu

1 / 2

How We Engineered a Three-Path Reward Processing System for a Real-Time Sports Platform

DEV Community: nextjs·GeekyAnts India Pvt Ltd·4 days ago
#ON8m8tXx
#devtonextjs#devto#dev#score#game
Reading 0:00
15s threshold

How one score event triggers 20+ reward evaluations across sync, async, and scheduled paths

1. The Problem

A player steps into one of our Core Soccer Tech pods, plays a 90-second game, and scores 847 points. The kiosk needs to respond instantly: show the score, trigger a celebration animation if they hit a personal high, and display any XP (experience points) earned.

But behind that single score, the system has to answer over 20 questions. Did they beat their high score? Did they unlock a new game mode? Did that score push them past a reward threshold? How many of today's seven daily missions did that game advance? What about the eight weekly missions running in parallel? And the eight seasonal missions that span the entire quarter?

All of this from one POST request.

The naive approach is to evaluate everything synchronously inside the score submission endpoint. The kiosk waits, the database holds a long transaction, and every player in the facility feels the lag.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.