Overview

Niantic is a gaming company best known for developing Pokémon Go, which has over 147 million monthly active users at peak usage. A game at this large level requires an elastically scalable database that can quickly respond to highly-concurrent queries. As a result, Niantic decided to build its own database service to handle these workloads.

In this video, Xinkai Wang, Staff Software Engineer at Niantic, reveals why Niantic chose TiDB’s TiKV — an open-source, distributed SQL key value store with built-in HTAP capabilities to power its database service.

Related Resources

How-Block-Migrated-to-a-Scalable-Data-Architecture-with-TiDB-0002

TiDB User Story: Why Block Selected TiDB

Why-Catalyst-Selected-TiDB-for-Its-Data-Serving-Layer-0003

TiDB User Story: Why Catalyst Selected TiDB

Databricks

TiDB User Story: Why Databricks Migrated to a Scalable Data Architecture

How-Block-Migrated-to-a-Scalable-Data-Architecture-with-TiDB-0002

TiDB User Story: Why Block Selected TiDB

Why-Catalyst-Selected-TiDB-for-Its-Data-Serving-Layer-0003

TiDB User Story: Why Catalyst Selected TiDB

Databricks

TiDB User Story: Why Databricks Migrated to a Scalable Data Architecture