TiDB, Powered by PingCAP

06/16/2026

The largest SaaS platforms collapsed data sprawl into a unified layer to survive at scale. Manus did the same thing to survive agentic AI. The pattern repeats for a reason.

The architecture playbook is the same. What changes is the workload shape.

Join TiDB's Field CTO Terry Purcell on June 25 as he walks through:
• The architectural arc from large-scale SaaS to production agentic AI
• How 60+ TiDB deployments handled complexity at their scale inflection points
• Where agentic workloads break previous-era limits — millions of tables, elastic capacity, persistent agent memory
• Real production lessons from companies like Manus

10:00–11:00 AM PT

Save your seat 👉 https://ow.ly/TYu950ZbLrJ

06/15/2026

Most agent stacks treat memory as an afterthought - a vector store bolted on, a context window stuffed full, a sync job running in the background hoping nothing drifts.

That's the wrong model. Agent memory is an infrastructure problem.

At Microsoft Build 2026, our Solutions Engineer Ravish Patel walked through the architecture that actually works: one TiDB table holding text, vectors, and metadata together — no separate vector store to sync, no two-system dance on every read.

The full write-up is now live, including:
• Copy-paste schema with native VECTOR(1024) columns and HNSW indexing
• Auto-embedding so the database generates vectors on insert — no pipeline to maintain
• Hybrid BM25 + vector search in a single query for when semantic similarity isn't enough
• The full Python loop using pytidb — three lines to store a memory, four to recall it

Build on TiDB Cloud Starter, free tier, no credit card required.

👉 https://ow.ly/voO250ZbIwb

06/03/2026

Most databases weren't designed for AI agents. TiDB Cloud + Amazon Bedrock changes that — unified HTAP, vector search, serverless branching, no separate systems. Full reference architecture on the AWS APN Blog.

🔗 https://ow.ly/STui50Z71uM

05/19/2026

Just 2 days until our live webinar with Plaid! 🎉

Zander Hill is walking through the full migration story: 234 databases, 6 engineers, and the playbook that made it work.

Join us Wednesday at 10am PST.
Register: https://ow.ly/3CU650YXLLl

05/12/2026

One week until our live webinar with Plaid's Zander Hill! 🎙️

He'll be walking through how Plaid migrated 234 databases from Aurora MySQL to TiDB: the team structure, the automation strategy, the risk playbook, and the lessons learned over 2.5 years.

Save your spot: https://ow.ly/izBU50YXLGW

05/05/2026

Most teams hear "234 databases" and immediately think: big team, long timeline, massive risk.

Plaid did it with 6 engineers, most without deep database expertise going in.

The secret wasn't headcount. It was how they scoped the project: aligning to business tolerances instead of engineering perfection, frontloading the riskiest Tier 0 services to de-risk everything downstream, and building automation that compounded with every migration.

Zander Hill is walking through the full story on May 21. Worth your hour.

📅 May 21 | 10-11am PST
Register: https://ow.ly/48Hq50YNvJ0

04/28/2026

Meet your speaker for May 21.

Zander Hill is Platform Architecture Lead at Plaid and the engineer who led one of the most quietly impressive database migrations in fintech. 234 databases. 100 services. A 6-person team. 2.5 years.

He's spent his career as CTO of a 50-person startup, Senior Director of Engineering, and leader of deeply technical backend organizations. He's bringing the unfiltered playbook to our webinar.

If your team is thinking about migrating off Aurora, you want to hear this one firsthand.

📅 May 21 | 10-11am PST
Register: https://ow.ly/Lwr150YNvA5

04/23/2026

There's a type of architectural debt that doesn't announce itself.

It builds in the gap between how your database was designed and how your application actually runs today, especially once AI workloads enter the picture. Unpredictable query patterns.
Concurrency profiles that don't match the original assumptions. Scale that arrived faster than the infrastructure could adapt.

The engineers solving this aren't waiting for it to become a crisis.

They're the people coming to TiDB SCaiLE Europe 2026.

Thursday, 4 June | Epicenter Stockholm.

Distributed SQL, agentic AI data architecture, and production-grade case studies from teams operating at real scale.

Spots are limited. Agenda dropping soon.
Register → https://ow.ly/vWcG50YNV1t

04/21/2026

234 databases. 6 engineers. Zero downtime.

We're bringing Plaid's Platform Architecture Lead Zander Hill on for a live webinar on May 21 to break down exactly how Plaid migrated 234 databases across 100 services from Amazon Aurora MySQL to self-hosted TiDB. In 2.5 years, with a small team, and three zero-downtime TiDB upgrades along the way.

If you're evaluating Aurora alternatives or planning a large-scale migration, this is the real-world playbook you won't find in documentation.

📅 May 21 | 10-11am PST
Register: https://ow.ly/UEVo50YNvhm

04/02/2026

Scaling often starts simple and ends messy: sharding workarounds, pipeline sprawl, and rising costs.

Join TiDB + XP2Cloud in-person to hear the Engie blueprint (10TB/day refresh patterns, in-app analytics, usage insights) plus a first look at TiDB X, our AI-native architecture unifying OLTP, analytics, and vector data.

RSVP:

Join TiDB for an in-person meetup where we break down how Engie runs production workloads on TiDB to handle its rapid growth.