Filter
Exclude
Time range
-
Minimum likes
A percentage needs both a numerator & denominator population. A ranking needs a defined comparison set. Explicit answer contracts capture these requirements before execution. Prevents logic errors like wrong counting units. #DistributedSQL #AI #OceanBase
1
32
Traditional architectures maintain two copies of truth: transactions and reports. Inconsistencies emerge during sync windows. Unified clusters eliminate drift—analytics query the same source data as transactions. #DistributedSQL #OceanBase
1
Analytical scans consume I/O bandwidth needed for transactional commits. Separating access paths within one cluster protects write latency from read-heavy queries. #DistributedSQL #Architecture #OceanBase
1
Row stores optimize point queries. Column stores optimize scans. Mixing workloads on one storage format forces trade-offs. Table-level storage formats allow distinct access paths within one cluster. #DistributedSQL #Database #OceanBase
4
Row stores optimize point queries. Column stores excel at large scans. One format for both guarantees trade-offs. Table-level storage enables workload-specific paths. #DistributedSQL #Architecture #OceanBase
1
Every additional system creates another boundary, pipeline, & copy. In an AI world, data movement itself becomes the bottleneck. The cost of moving data deserves more attention than it gets. #DistributedSQL #CloudNative #OceanBase
3
Multi-step questions need multi-step plans. Simple lookups stay simple; complex tasks get execution paths covering joins & computation. #DistributedSQL #AI #OceanBase
4
Setting a global precedent for distributed systems powering core banking engines of tier-one flagship banks. #Banking #DistributedSQL #OceanBase
2
Core system cutover touches countless peripheral systems. A territory where no distributed database globally had substantial prior experience. #DistributedSQL #FinTech #OceanBase
1
Maintaining two systems means coordinating two copies of data. Inconsistencies arise during synchronization windows. A unified cluster ensures transactions & analytics query the exact same source truth. #DistributedSQL #Database #OceanBase
6
Our Founding Partner, @KabileshPr , spoke at the Chennai Reliability Engineering meetup on Distributed SQL with YugabyteDB, focusing on real-world production failures and failovers. Thanks to Sharmila S and MX Technologies for hosting us! #YugabyteDB #DistributedSQL #SRE
39
We're at AI Summit Barcelona, 22–23 September, Booth E4. Our very own Bernard Kavanagh is on stage 23 September at 13:40: "Breaking the Memory Wall: Durable Memory for AI Agents at Scale." More details: pingcap.com/event/join-tidb-… #AIAgents #AIInfrastructure #DistributedSQL #TiDB
1
2
290
Aurora's write ceiling isn't a tuning problem — it's architectural. One primary writer. No horizontal write scaling. Full breakdown: ow.ly/9LXM50Zl00m #Aurora #DistributedSQL
3
5
230
Atlassian's Forge platform: one schema per tenant, 3 million+ tables, one TiDB cluster. The engineering story behind how that actually works 👇 ow.ly/piRb50ZjwH9 #TiDB #Atlassian #DistributedSQL #SaaS
2
5
599
Distributed SQL is a class of cloud-native, highly scalable, and resilient databases designed for today’s always-on, data-driven world.💪 Download the Distributed SQL Databases For Dummies (2nd Yugabyte Special Edition) eBook and explore how #distributedSQL can help you achieve ultra-resilience, simplify operations, accelerate innovation, and future-proof your next #GenAI applications. Find out more and get your free copy today!⬇️ na2.hubs.ly/H06gyf50
1
2
163
Most AI agents fail not due to models but data layers. Join Mattias Jonsson at #GitexEurope Berlin, 1 July, 10:40am, Hall 2.2. #AgenticAI #DistributedSQL #TiDB #AIInfrastructure
1
2
3
222
Great conversations at DevOps Conclave 2026 — platform engineers, SREs, and architects thinking seriously about distributed SQL at scale. Missed us? Demo here → ow.ly/9Gby50ZbItW #DevOps #TiDB #DistributedSQL
2
5
296