TanStack DB - Expo/SQLite adapters, Best practices, and Roadmap
Iâve been exploring TanStack DB as a replacement for TinyBase in my app. I specifically need the differential dataflow and derived values capabilities for complex aggregations/analytics, which are difficult to manage in my current setup.
I have a few questions regarding persistence and roadmap:
1. Recommended approach for Expo SQLite (without RxDB)
I need to persist data to Expo SQLite. Since the RxDB adapter is cost-prohibitive for my use case, I am planning to use on-demand mode.
My Plan: Implement the query function to manually handle reads/writes to Expo SQLite (via an ORM or direct API) and in future adding sync to Firestore.
Question: Is this a valid pattern for TanStack DB, or is there a recommended "better way" to bridge to a custom SQL store right now?
2. Web Persistence (IndexedDB)
For the web version of the same app, I want to avoid LocalStorage due to it's limitations.
Question: Are there plans to support IndexedDB or WASM SQLite as first-class adapters/collections in the near future?
3. Contributing
I am interested in contributing to these adapters if they aren't planned yet. However, I am a Java developer just starting with TS/Mobile.
Question: What is the complexity level for writing a new storage adapter? Would this be achievable for a beginner in the TS ecosystem?
appreciate any suggestions or recommendation
Thanks!
I have a few questions regarding persistence and roadmap:
1. Recommended approach for Expo SQLite (without RxDB)
I need to persist data to Expo SQLite. Since the RxDB adapter is cost-prohibitive for my use case, I am planning to use on-demand mode.
My Plan: Implement the query function to manually handle reads/writes to Expo SQLite (via an ORM or direct API) and in future adding sync to Firestore.
Question: Is this a valid pattern for TanStack DB, or is there a recommended "better way" to bridge to a custom SQL store right now?
2. Web Persistence (IndexedDB)
For the web version of the same app, I want to avoid LocalStorage due to it's limitations.
Question: Are there plans to support IndexedDB or WASM SQLite as first-class adapters/collections in the near future?
3. Contributing
I am interested in contributing to these adapters if they aren't planned yet. However, I am a Java developer just starting with TS/Mobile.
Question: What is the complexity level for writing a new storage adapter? Would this be achievable for a beginner in the TS ecosystem?
appreciate any suggestions or recommendation
Thanks!
