TiDB Adoption at Pinterest
To replace HBase, Pinterest evaluated over 10 datastore technologies against criteria including reliability, performance, functionality, and community support. After initial screening, three options remained: TiDB, YugabyteDB, and DB-X. Shadow traffic testing with production workloads revealed TiDB's stability and sustained performance. Reliability tests confirmed TiDB's resilience and lack of fundamental flaws. TiDB's deployment at Pinterest uses Teletraan, an in-house system, but migration to EKS is planned as Kubernetes support matures. Three-way replication and read-only replicas reduce storage costs compared to HBase's six replicas. TiDB is currently deployed in a single AWS region with three replicas in different AZs for fault tolerance. Communications are protected using mutual-TLS and CNAME validation, with Envoy as the proxy to the SQL layer. Pinterest is exploring multi-region setups and removing Envoy to enhance control over connections.