[Tracking] Onyx Improvements

[fabioh8010]

Summary

This issue tracks ongoing and future work to improve Onyx, following the completion and review of the original audit work.

While the audit focused on performance and scalability, current efforts are shifting toward simplifying Onyx internals. Over time, incremental optimizations and feature additions have increased internal complexity, making changes harder to reason about, test, and evolve safely. Addressing this complexity is necessary to improve correctness and maintainability, and to enable future performance work without introducing additional risk.

This issue replaces the original audit issue as the primary coordination point for Onyx improvements.

As a start point we will be focusing on the simplification of useOnyx API, namely the initWithStoredValues, allowStaleData, canBeMissing and allowDynamicKey options.

• [Due for payment 2026-02-19] [Onyx Audit] Remove initWithStoredValues from useOnyx #80091
• [Onyx Audit] Remove allowStaleData from useOnyx #80094
• [Due for payment 2026-03-04] [Onyx Audit] Remove canBeMissing from useOnyx #80095
• [Onyx Audit] Remove allowDynamicKey from useOnyx #80096

Additionally, we already have some efforts in Onyx internals to simplificate and improve its performance:

• [Onyx Audit] Batching mechanism feels overcomplicated #71207
• [Due for payment 2026-02-16] [Onyx Audit] Remove Outdated Batching Mechanism from Onyx #79338
• [Onyx Audit] Performance improvements to SQLiteProvider #80243
• [Onyx Audit] Investigate SQLite for Web #80245

Issue Owner

Current Issue Owner: @fabioh8010