Client: OddsForge · iGaming & Betting · Maltese online sportsbook

Reducing Bet Placement Latency for a Sportsbook

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supplied dedicated L2/L3 engineers for OddsForge’s Java and Kafka sportsbook. In a four-week pilot, the client’s Datadog monitoring recorded p95 bet-placement latency falling from 840 ms to 244 ms in the measured tournament window.

Client and engagement facts

Client
OddsForge
Industry
iGaming & Betting
Business context
Maltese online sportsbook
Delivery model
L2/L3 staff augmentation
Application
Bet-placement API with Kafka pipeline and settlement workers
Supplied geography
Maltese

Application stack and tools

Application stack

  • Java/Spring
  • Kafka
  • Redis
  • PostgreSQL
  • EKS

Tools used

  • Datadog
  • PagerDuty
  • Grafana
  • Jira

Why Support Was Needed

During tournaments, bet requests competed with settlement workers for the same Kafka partitions. The sportsbook used staff augmentation to keep incident command and production approval with its own team.

Technical Work

  • Reproduced the peak slowdown in staging with a 20-minute load test.
  • Identified partition skew, long poll intervals and garbage collection pauses.
  • Rebalanced partitions and added a partition-level Kafka lag alert in Grafana.

Representative Incident

During a quarter-final, one Kafka partition drew 38% of traffic after a consumer restarted with stale metadata. The on-call engineer paused the consumer and rejoined the group. Flow recovered in 11 minutes, and the team added a check 30 minutes before kickoff.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
p95 bet-placement latency840 ms244 msms4-week pilotClient Datadog
Peak-week incidents1424 weeksClient PagerDuty; Scope: The four-week pilot excluded two vendor-feed incidents from the platform incident count.
Kafka lag alerts31/wk4/wk/wk4 weeksClient Grafana

Evidence and Limitations

The four-week pilot excluded two vendor-feed incidents from the platform incident count. Tournament volumes varied. The peak-week comparison uses the quarter-final window.

Onboarding and Change Approval

Onboarding took seven business days, including the client interview. The engineers received least-privilege read access, and OddsForge approved production changes through Jira.

Scope a Similar Engagement

Describe the API, the peak window and the incident class your lead wants a dedicated engineer to own. Request a support plan or explore dedicated support engineers.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.