South Asia ke sabse popular betting product ka tech breakdown — Hinglish mein, developers aur founders ke liye.
Agar aapko kabhi "exchange panel" ka client brief mila hai aur samajh nahi aaya ki ye hota kya hai — ye ek betting exchange hai (back/lay, position matching, commission model) jo multi-level credit hierarchy ke andar wrapped hai. Engineering ke teen interesting problems:
1. Credit hierarchy = ledger problem
Admin → Master → Agent → Player — har settlement 3–5 levels mein atomically propagate hota hai. Double-entry ledger chahiye, per-level P&L rollups ke saath. Ek session mid-match settle hota hai toh hazaaron accounts update hote hain — aur har level ka dashboard paisa-paisa match hona chahiye, warna network ka trust (jo asli product hai) khatam.
2. Ball-by-ball repricing = event stream problem
Session markets har delivery par reprice hote hain. Feed layer (Diamond-format APIs: match odds, bookmaker, fancy, session, result) ke updates sub-second mein saare clients tak fan-out hone chahiye, aur wicket girte hi market suspend — stale price snipe hone se pehle. Suspension latency ka seedha matlab paisa hai.
3. Risk = real-time aggregation problem
Live exposure per market/user/agent, limits, bet-delay windows, winning-account profiling. Frontend nahi — ye module decide karta hai ki operator profit mein rahega ya nahi.
Delivery reality
Scratch se koi nahi banata: ready panels 1–3 hafte mein deploy hote hain (feeds, casino APIs, themes pre-integrated), custom deployments 4–8 hafte. Build vs buy ka pura math maine sportsbook cost article mein cover kiya tha.
Operator-side full guide (Hinglish): Cricket Exchange Panel Kaise Banaye
Top comments (0)