Tidb

TiDB's core argument is consolidation. Most agent stacks in 2026 run a vector database for retrieval, Postgres or MySQL for state, and a warehouse for analytics — three systems, three consistency models, and a sync job between them. TiDB's pitch is that a vector similarity search can be joined against live transactional rows in one SQL statement, which is the whole reason it exists. The docs example joins a memory_store table ranked by vec_cosine_distance against an agent_tasks table; that single query is the product in miniature. The AI-facing features are real, not marketing borrow. Per-agent isolation gives each agent its own persistent context without noisy neighbors. Native vector indexing and RAG pipelines live in the same engine as ACID transactions, so agent state survives a workflow step change. TiDB Cloud provisions agent-created databases in under a second, which is what lets Kimi's K2.6 agent spin up an isolated database per generated site. Autoscaling scales down to zero when idle, and instant branching gives you isolated environments for testing agent changes. Strengths worth naming: MySQL 8.x compatibility keeps migration paths short for the large population of teams already on MySQL; TiCDC covers real-time change data capture; compute and storage scale independently; and point-in-time recovery with log compaction is a genuine operational safety net. The customer evidence is unusually concrete — Plaud's 10x QPS improvement and elimination of S3 retrieval latency, Atlassian's 500K concurrent connections per cluster, Rakuten's 17ms average at 25K writes/sec. Weaknesses are mostly operational. Distributed SQL is not a light-touch stack: if your team has no SQL or Kubernetes depth, self-managed TiDB will be a burden, and the managed tiers exist precisely because that burden is real. TiDB Cloud Essential runs roughly $20/day for a typical small production footprint, which puts it well outside hobby-project budgets. Multi-region deployments with strict ACID and low single-digit latency requirements are a poor fit because distributed consensus has physics attached to it. And the cloud-only enterprise features (CMEK, PrivateLink, VPC Peering at the Premium tier starting from $1800/mo) mean the fully open-source path does not include everything PingCAP sells. Where it fits: agent platforms that need durable memory behind ACID guarantees, teams consolidating hundreds of sharded MySQL or Postgres clusters into a handful of global ones, and companies that want HTAP analytics without standing up a separate warehouse. Where it does not: embedded or edge use cases, non-technical teams wanting a turnkey product, and anything where a $20/day floor already exceeds the budget.