# cricket Published articles for cricket. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The bot that lied to cricket fans with a straight face: Temporal x San Francisco Unicorns DevFeed: [The bot that lied to cricket fans with a straight face: Temporal x San Francisco Unicorns]() Original publisher: [Read original article]() Author: Shubham Londhe Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Bot](), [trust](), [data]() Tags: [cricket](), [execution](), [gemini](), [temporal-voices](), [trust](), [whatsapp]() ### AI overview A Temporal developer advocate describes building a WhatsApp bot for San Francisco Unicorns cricket fans. Gemini handled conversation while Temporal managed reminders, live-score polling, and durable execution; a live-score failure highlighted the importance of trust and reliable data. ### Source excerpt How a WhatsApp bot for San Francisco Unicorns cricket fans lied about a live score at 3 AM, and what durable execution with Temporal taught us about trust. ## How Dream11 Built a Real-Time AI Sports Streaming Companion DevFeed: [How Dream11 Built a Real-Time AI Sports Streaming Companion]() Original publisher: [Read original article]() Author: Dream Blog Published: 2026-06-15T09:51:14Z Content type: tutorial Language: en Sources: [Dream11 Engineering]() Topics: [AI Agent](), [Streaming](), [Artificial Intelligence](), [real-time](), [voice ai](), [Sports]() Tags: [agent](), [ai](), [ai-agent](), [creators](), [cricket](), [latency](), [real-time](), [sports](), [streaming](), [tech](), [voice](), [voice-ai]() ### AI overview This developer article describes Dream11's AI Companion, a multilingual voice AI agent that joins live creator streams as a co-host. It explains that the system watches matches, reacts to events, interacts with creators and audiences, hosts trivia, and supports live cricket commentary with approximately two-second voice latency. ### Source excerpt Written by Narayan Sharma, Rajesh Mohanty, Dhruv Nigam, Chetna Meena and Palash TatteThe Moment That Sparked Everything Picture this: a live cricket stream. A boundary flies to the fence. The creator reacts; screaming, laughing, and enjoying the moment. The audience piles on in the chat. And in the corner of the screen, a street-smart monkey named Googly Bhai mutters: "Bhai kya cover drive mara Kohli ne, ball field pe aise glide kar rahi hai jaise garam parathe pe makkan!" The audience erupts. Not because it was scripted. Not because a human typed it. But because AI watched the same ball, processed the same moment, and reacted, with personality, with timing, and with an opinion, in under two seconds. That's the Dream11 AI Companion. And building it was anything but simple. 🏆 World's first real-time AI sports streaming companion ⚡ ~2 second end-to-end voice latency 🗣 70+ languages supported natively by S2S model; primary: Hindi, English, Hinglish 🔌 Zero extra setup for streamers -- integrates directly via OBS + Creator Console What We Set Out to Build With 250M+ users, Dream11 has been on a journey to become everyone's sports entertainment destination. And entertainment lives where the fans are; inside live streams, creator channels, match-day conversations. The question we asked ourselves: What if a creator never had to stream alone again? Or if they were unavailable, could we ensure they had a back up? The answer was an AI Companion: A real-time, multilingual voice AI agent that joins live creator streams as a co-host. It watches the match. It reacts to what's happening. It banters with creators and audiences. It hosts trivia. It roasts players. It debates cricket. Meet the Characters Before we get into architecture, meet the two AI characters at the heart of this product. Bittu Bindas 🐻 A bold, banterous bear. Speaks Hindi (in Mumbaikar style). Playful, opinionated, and absolutely no-filter. Bittu doesn't overthink. He just says what every fan in the room is think ## Inside the Tech That Powers Dream Cricket's Multiplayer Experience DevFeed: [Inside the Tech That Powers Dream Cricket's Multiplayer Experience]() Original publisher: [Read original article]() Author: Dream Blog Published: 2025-12-13T07:38:59Z Content type: article Language: en Sources: [Dream11 Engineering]() Topics: [Kubernetes](), [cloud-infrastructure](), [Open Source](), [Server]() Tags: [architecture](), [cloud](), [cricket](), [deploy](), [game-development](), [game-servers](), [games](), [gaming](), [high-performance](), [infrastructure](), [kubernetes](), [latency](), [multiplayer](), [open-source](), [production](), [scale](), [tech]() ### AI overview This article describes how Dream Cricket scaled its multiplayer infrastructure after a simple queue and fixed server pool could no longer handle growing adoption and large-scale events. It discusses challenges including peak matchmaking delays, unfair pairings, idle capacity, risky rollouts, and limited operational visibility, then outlines a design using Open Match, Agones, Kubernetes, and a health and latency service. ### Source excerpt By Vaibhav Naik Every great game starts with great tech -- and great people behind it. If you're passionate about crafting seamless, high-performance gaming experiences that bring players closer to the sport they love, we'd love to have you on our team. Explore our open roles at Dream Cricket. Why Multiplayer Matters on Dream Cricket We've always believed that the best games are the ones that bring people together. And that's exactly what multiplayer on Dream Cricket does -- it turns gaming from a solo challenge into a shared moment. The banter, the thrill of a close finish, the satisfaction of a fair match -- that's what keeps players coming back. Over the years, as our player base grew and expectations rose, we knew our multiplayer system needed to be scaled. It had to be faster. Fairer. The kind of system that doesn't break under pressure, whether it's lakhs of players logging in during a live event or two friends battling it out over spotty mobile data. This blog is our story of getting there. It's about how we rethought everything, from how we match players to how we run thousands of servers all at once. You'll get a look at the roadblocks we hit, the calls we had to make, and how open-source tech like Open Match and Agones helped us build something truly scalable. Building for the Next Era of MultiplayerThe Challenge Our initial multiplayer setup used a simple queue and a fixed pool of servers, which worked well. As adoption grew and large-scale events became frequent, the system was unable to manage the load. We had to move from basic matchmaking to skill-based fairness, surge handling, safe releases, and cloud portability. And as we scaled, familiar pain points surfaced: High P95 time-to-match at peak; cancellations rose Unfair pairings in upper tiers; noticeable re-matches Idle server waste off-peak; slow warm-up during spikes Risky rollouts without clean canaries; limited on-call visibility The challenge was clear: we needed to decouple matchmaking logic from