On September 24, a GlobeNewswire announcement put Nepal in the spotlight: three local brands, MJ88, 8MBets, and NPL11, announced they had successfully launched microservices architecture platforms, becoming the first operators in South Asia to do so, with peak concurrent online users able to handle over 10,000. All three are new faces, none of them were split off from legacy systems, and all adopted microservices from the very first line of code.
For a small market, 10,000 concurrent users is a threshold. On match days, during reward distributions, and for campaigns, traffic all crowds into a few hours. Monolithic architecture requires scaling the entire machine together, while microservices only scale the specific component that cannot keep up, making costs manageable. Another figure from NPL11 is even more solid: the video latency for live dealer content from camera to player screen is only 100-200 milliseconds. This metric is called glass-to-glass in the industry, and it is enough to directly match the pace of international event live streaming.
NPL11's approach is multi-category integration: sports events, live dealer, electronic games, esports, and other categories share one account, so players do not need to shuffle between multiple wallets. For the operations side, the significance is even greater: unified data standards, campaign configurations take effect once, and there is no need to maintain a separate backend for each category.
This case gives teams currently evaluating platform solutions a new reference. The common route is to launch monolithic first, then split after it works, but these three did the opposite: new market, new brands, starting directly with microservices. The advantage is that when peaks come, you scale by component; the disadvantage is that from the start there are requirements for engineering capability and the maturity of gaming API integration. When comparing against the capacity planning checklist for high-concurrency architecture, you can ask suppliers one more question during selection: is the 10,000 concurrency figure from stress testing, or copied from a configuration table.
Teams that are unsure can contact us to break down and calculate the costs and timelines of both the microservices and monolithic paths.