Leo Zeba
@leozeba.bsky.social
That's perfect!
For my applications, I rely on object storage as the single source of truth. Each user has their own S3 prefix and SQLite database, with downloadable WebAssembly (WASM) business logic.
Works like a charm!
For my applications, I rely on object storage as the single source of truth. Each user has their own S3 prefix and SQLite database, with downloadable WebAssembly (WASM) business logic.
Works like a charm!
December 1, 2024 at 6:45 PM
That's perfect!
For my applications, I rely on object storage as the single source of truth. Each user has their own S3 prefix and SQLite database, with downloadable WebAssembly (WASM) business logic.
Works like a charm!
For my applications, I rely on object storage as the single source of truth. Each user has their own S3 prefix and SQLite database, with downloadable WebAssembly (WASM) business logic.
Works like a charm!
we've done something like this at memori.as with 3 sqlite databases per account.
- private data is local first and synced to private.db
- friend groups write data to shared.db (to, from) with read-only access to everyone in from list
- public.db is for everyone
- ui handle data from all databases
- private data is local first and synced to private.db
- friend groups write data to shared.db (to, from) with read-only access to everyone in from list
- public.db is for everyone
- ui handle data from all databases
November 22, 2024 at 11:17 PM
we've done something like this at memori.as with 3 sqlite databases per account.
- private data is local first and synced to private.db
- friend groups write data to shared.db (to, from) with read-only access to everyone in from list
- public.db is for everyone
- ui handle data from all databases
- private data is local first and synced to private.db
- friend groups write data to shared.db (to, from) with read-only access to everyone in from list
- public.db is for everyone
- ui handle data from all databases