desertthunder.dev
a love letter to tangled (android, iOS, and a search API)
1---
2title: ADR Research - Turso For Production Search
3updated: 2026-03-26
4status: superseded
5---
6
7## Status
8
9This research record is kept for history. It no longer describes the active
10deployment direction.
11
12## Historical Summary
13
14Turso was originally attractive because Twisted already used SQLite-style
15queries, migrations, and FTS5 search behavior. It offered the shortest path
16from local file-backed development to a remotely hosted production database.
17
18## Why It Was Superseded
19
20The project has now chosen PostgreSQL plus Coolify instead.
21
22Main reasons:
23
24- Twisted now runs as multiple long-lived services against one shared database
25- the project wants standard production operations and restore tooling
26- local and production environments should converge on one database family
27- the cost of carrying Turso-specific behavior forward outweighed the migration
28
29## What Still Matters From This Research
30
31- rebuilding the dataset from upstream sources remains the safer default than
32 promoting an experimental local database
33- embedded-replica ideas were interesting but were not a fit for the Go stack
34 the project kept
35- search behavior changes must be treated as product-visible, not just as a
36 storage swap
37
38## Current Source Of Truth
39
40See `docs/adr/storage.md` for the accepted storage decision.