3 ms·
Sorry if the post sounds too marketing-heavy. I'm sharing this case study because it addresses a common technical challenge: scaling a high-traffic application
by jinqueeny 2y ago
Sorry if the post sounds too marketing-heavy. I'm sharing this case study because it addresses a common technical challenge: scaling a high-traffic application (Kwai, a video platform) from traditional MySQL to a distributed database system. It describes the journey from managing 300+ MySQL shards to consolidating into a single 400TB cluster using OceanBase, handling over 1 million QPS during peak loads. While the post is oriented towards promoting OceanBase, it resonated with developers because it provides specific technical details about real-world scaling problems, architecture decisions, and performance metrics that many engineering teams face when growing beyond traditional MySQL setups.
- theideaofcoffee 2y agoThis comment pegs my AI-slop-o-meter scale high. No real human genuinely talks like this. Perhaps sharing specific problems you ran into in your single host to distributed sql journey that this product solved for you would be useful? That would be much more interesting than a post about a marketing page and Someone Else’s Problem.
- askthrowaway 2y agoYour AI-slop-o-meter needs calibration
- cr125rider 2y agoAI-slop-o-makers were trained heavily on marketing-speak and they often sound very similar.
- tuananh 2y agoare you working for OceanBase?