Please turn JavaScript on
Homepage
TrendingMy newsFind FeedsDelivery settingsPlansMy earnings
HelpBlog
Log in
Find more feeds
header-image

TiDB

follow.it gives you an easy way to subscribe to TiDB's news feed! Click on Follow below and we deliver the updates you want via email, phone or you can read them here on the website on your own news page.

You can also unsubscribe anytime painlessly. You can even combine feeds from TiDB with other site's feeds!

Title: TiDB, Powered by PingCAP

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.27 / day

Message History

How to Build an AI App That Simulates Life Decisions
Key Takeaways Build an AI-powered life simulator app generating realistic 6-24 month outcomes across 6 life dimensions (financial, emotional, career, health, relationships, overall). 6 embeddings per decision enable targeted semantic search across specific life dimensions instead of diluted generic results. TiDB combines vector search + SQL joins in single queries and...

Read full story
SingleStore vs TiDB: A Guide to Choosing the Right Distributed SQL Database
Key Takeaways SingleStore uses an aggregator–leaf design with “Universal Storage,” while TiDB is layered (TiDB SQL + TiKV row store + TiFlash columnar). SingleStore replicas are asynchronous (eventual windows); TiDB is strongly consistent (linearizable) via Raft. SingleStore relies on hash partitioning with partition counts set at creation; TiDB auto-...

Read full story
Solving the Distributed Backup Headache: How TiDB Delivers Transactional Consistency
Key Takeaways Unlike traditional systems that copy raw storage files, TiDB anchors backups to a single, globally consistent timestamp. By using a cluster-wide boundary, TiDB avoids “fractured” backups where different nodes reflect conflicting transactional states. Committed data is recorded, enabling precise Point-in-Time Recovery (PIT...

Read full story
Raft Region Size: The Invisible Lever for Distributed Database Performance

If you have ever tuned a distributed database, you have probably adjusted obvious knobs: CPU, memory, replication factor, concurrency limits. But there is a quieter setting, one that rarely gets headlines, that has an outsized impact on performance, reliability, and operational sanity: Raft region size.

In


Read full story
The Hidden Cost of Database Over-Provisioning

According to the 2025 Kubernetes Cost Benchmark Report, average CPU utilization across Kubernetes clusters is approximately 10 percent. For many teams, that raises an obvious question: why is database utilization so low?

The answer is not poor engine...


Read full story