Tacnode™
Pipelies2 min

The Crowded Total: A $10K Bet Accepted with $4K of Room Under the Cap

Liability on a home win: $186,000. Bets accepted in the last second have already taken it to $246,000. It's late in the game. Liability on a home win is $180,000, against a cap of $250,000. Then the home team scores, and bets pour in on a home win. Within a second real liability is $228,000, and the published total still says $180,000. The stream job is still counting. It publishes $186,000, and every bet check reads that. The real number is $246,000. A $10,000 bet arrives. The check sees $64,000 of room under the cap and accepts it. There was $4,000, and hundreds of other checks made the same call. Then the same two seconds with accepted bets written to Tacnode. Each check reads liability that includes the bets accepted a moment before. This bet would cross the cap, so it's declined. Accepted bets are written to Tacnode, and liability is computed from them. The bets and the total live in the same place, so the cap holds when the burst arrives. Pricing, trading and settlement stay in your systems.

Overview

One of the fourteen Pipelies lies: how a stream job that is still counting lets bets through past the liability cap after a goal, and the same two seconds with accepted bets written to Tacnode.

Topics Covered

  • •A $250,000 liability cap late in the game
  • •A goal, and a burst of bets on a home win
  • •A published total that trails the bets already accepted
  • •A $10,000 bet accepted with $4,000 of room
  • •Liability computed from the accepted bets themselves

Key Takeaways

  • ✓Every check read the last total the stream job published
  • ✓Hundreds of checks made the same call in the same second
  • ✓With accepted bets written to Tacnode, each check reads liability that includes the bets accepted a moment before
  • ✓Pricing, trading and settlement stay in your systems

Ready to get started?

Book a demo to see how Tacnode can power your real-time data infrastructure.