Tacnode™

Late market suspension in in-play betting

After a goal, a sportsbook accepts bets at the pre-goal price for seven seconds, because the suspension reaches bet acceptance through the odds pipeline.

Photo: Alex Simpson / Unsplash
→→At62:00
The story

A sportsbook takes bets during a live match.

  • Harbor City and Northgate, 0–0. Harbor City to win is +240: a $100 bet wins $240.
  • The trading team sets the prices. An odds pipeline carries every price change to a cache, which serves the apps.
  • When a bet comes in, bet acceptance checks that cache: is the market open, and is this still the price?
The sportsbook’s trading screen
Live62:00
Harbor City
0–0
Northgate
Match resultOpen
Harbor City
+240
Draw
+190
Northgate
+130
Incoming bets · Harbor City to win
  • fan$10@ +240Accepted
  • fan$25@ +240Accepted
What’s happening underneath
readsTrading systemTrading platformpricing the matchOdds pipelineKafkanormal loadOdds cacheRedisopen · +240Sportsbook appsBettorsBots · fansBet acceptanceBet placement serviceaccepting
1 / 9

Illustrative scenario. Timings show the shape of the problem, not a measurement of any one company.

Watch the walkthrough

Video
4:27
Past-Posting in Live Betting: Why Sportsbooks Keep Taking Bets After a Goal
Alex Kimball walks through this replay: a sportsbook keeps taking bets at the pre-goal price for seven seconds after a goal, and the same goal with current context.
Watch on YouTube

Your stack today, and with the Tacnode Context Lake™

Today

Trading system
Trading platform
Odds pipeline
Kafka
Suspension queued behind odds updates
Odds cache
Redis
Bet acceptance
Bet placement service

Most sportsbooks move a suspension the same way they move a price: the trading system publishes it to a pipeline, and a cache serves it to the app and to bet acceptance. That path was built to fan prices out to millions of screens, where a few seconds of delay is acceptable. Bet acceptance needs the suspension the moment it is decided. After a goal the pipeline carries its heaviest load, and anyone with a faster feed than the cache can bet on a price that no longer matches the match.

With the Tacnode Context Lake™

Trading system
Trading platform
Tacnode Context Lake™
Market suspended at 62:14
Bet acceptance
Bet placement service
  • The decision and the bets are in one placeThe trading team writes the suspension where bet acceptance reads, instead of sending it down a pipeline built to fan prices out to screens.
  • Bets are checked against current stateBet acceptance reads the latest committed state, not a cache waiting on the pipeline, so bets at the pre-goal price are rejected from the first second.
  • Every accepted bet is written backLiability on each outcome includes every bet already accepted when the next one arrives.

Questions to ask your team

  1. 1How many seconds pass between a goal confirmed in your trading system and bet acceptance seeing the market suspended?
  2. 2Does bet acceptance read suspensions and liability from the same cache that serves odds to the app?
  3. 3How much do you pay out each season on bets accepted after a goal, a card or a point that should have closed the market?