outline the general direction of YugabyteDB, Inc.ʼs (“Yugabyteˮ) offerings. It is intended for information purposes only and may not be incorporated into any contract. Any information regarding pre-release of Yugabyteʼs offerings, future updates or other planned modifications is subject to ongoing evaluation by Yugabyte and is subject to change. This information is provided without warranty or any kind, express or implied, and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions regarding Yugabyteʼs offerings. These purchasing decisions should only be based on features currently available. The development, release, and timing of any features or functionality described for Yugabyteʼs offerings in this presentation remain at the sole discretion of Yugabyte. Yugabyte has no obligation to update forward-looking information in this presentation. SAFE HARBOR STATEMENT 2
2x per year YYYY.1 and YYYY.2 ◦ Maintenance releases ~monthly YYYY.1.0, YYYY.1.1, .. ◦ Patch releases as needed (4th digit) • Support Lifecycle: ◦ YYYY.1 will be STS 12+6 months * ◦ YYYY.2 will be LTS 24+12 months** Updated YBDB Cadence & Support Lifecycle Overview • Self-explanatory naming • Increased / extended support lifetime • Improved quality • Greater predictability Why does it matter? GA in 2.20.x 5 * Fixes + call support. This is an increase from 8+6 months ** Fixes + call support. This is an increase from 18+6 months
2x per year TBD.0, TBD.0, etc. ◦ Minor releases ~ monthly TBD.0, TBD.1, ..., up to TBD.5 ◦ Patch releases as needed (3rd digit) • Support Lifecycle: ◦ 6 + 8 months * • New features appear only on minor releases of current major train Updated YBA Cadence & Support Lifecycle Feature Overview • Enables picking up new YBA features quickly • Fewer YBA branches → focus → higher quality • Upgrade YBA independently from DB • Customers must upgrade YBA 2x per year for fixes Why does it matter? GA in 2.20.x 6 * Fixes + call support. This is a change from STS (8+6 months) and LTS (18+6 months)
FALL BACK 21 アプリは従来のDBソース)にアクセス （データは最新） yb-voyager initiate cutover to source ソースへのカットオーバーを実施 ターゲットからソースへのデータ複製停止 FALL BACKを実施した状態) ターゲットへのカットオーバー実施後 ターゲットからソースへのデータ複製は継続 アプリが新しいDBターゲット)にアクセス後、不具合 発生 X
hardware: Allows YBDB to use max hybrid clock offset thatʼs absolutely-bounded (e.g. 1.5ms) instead of conservatively-assumed 500 ms • Significant improvements on speciality hardware: On some AWS nitro instances the offset can be reduced by 10x (to 100 usec) • Requires new provisioning steps with sudo/root: Install clockbound daemon and client. Precision Time Sync Improvements can dramatically improve P99 latencies for some workloads Feature Overview • Improves P99 latencies for certain workloads • Workloads improved: those with near-simultaneous reads & writes to the same row ◦ How: instead of backing off & retrying, we reduce (or eliminate on AWS) the back-offs & retries Why does it matter? 28 In Preview
and will improve perf results by eliminating cross-region latencies • Was xCluster a topology tested in the eval? • It wonʼt suffer from cross-region “laws-of-physicsˮ latencies. • xCluster should deliver “localˮ latencies & performance (unlike Stretched Cluster) xCluster Async replication between two clusters in different regions Region 2 Region 3 Region 1 Stretched Cluster Sync replication across regions within a cluster 30
• Utilizes lower-level XCluster Replication to move the bits asynch • DR Runbook automation (e.g. promote/demote, resync after extended network outage, etc.) • Limitations: DDL changes (add table, index, etc) need careful handling xCluster DR provides a turnkey Solution for DR w/ failover and switchover orchestration Feature Overview • Business continuity with low RPO & RTO from unplanned region or datacenter outages • Regular BC/DR testing with zero RPO/RTO • Supports regulatory compliance initiatives Why does it matter? 31 DR Primary Read/write) DR Replica Read-only) Past: GA in 2024.1.2
Native Bootstrapping of Secondary Cluster Disaster Recovery DR 2025 Plans Features Planned • Avoid pain dealing with DR configuration related operational failures • Save time with 1-click DR setup Why does it matter? 32 Before: After: For all DDLs (e.g. creates, drops, alters) Step 1 Execute on Primary Step 2 Execute on Replica Execute on Primary ** Applicable to xCluster DR and xCluster Replication (SQL xact mode); does not apply to xCluster Replication (SQL non-xact, CQL, nor bi-directional)
MongoDB alternative • PostgreSQL extension that adds native support for BSON and MongoAPIs • Built by Microsoft and donated to the Linux Foundation ◦ Powers vCore-based Azure Cosmos DB for MongoDB • Founding members: Microsoft, AWS and Yugabyte • YugabyteDB, a PostgreSQL fork that supports the DocumentDB extension
yugabytejapan
qa
dayjournal
nakasho
zozotech
shomaekawa
iwamot
shift_evolve
brainpadpr
msyksphinz
kaminashi
nobu09
hattori
stephaniewalter
3n
lara
csswizardry
panda_program
bkeepers
lauravandoore
eitanlees
lynnandtonic
tammyeverts
danielanewman
sachag
