Pocketbase: Open-source back end in one file

Re:Pocketbase: Open-source back end in one file by blackoil on Sunday January 07, 2024 @06:47AM (#38900446)

More than one server. Sqlite should be thread safe and simple services can scale to thousands of parallal users. If you are OK with some downtime every 6 months when server goes down it will scale well. Deploy/ rollback will be an effort.

[ Parent | on HN ]

Re:Pocketbase: Open-source back end in one file by WM6v on Sunday January 07, 2024 @07:48AM (#38900793)

Gotcha. And that makes sense for the purpose of the project. Should one have multiple instances of sqlite dbs, what strategies exist to keep them synced?

[ Parent | on HN ]

Re:Pocketbase: Open-source back end in one file by ozim on Sunday January 07, 2024 @07:05AM (#38900553)

Downside with separate SQLite databases will be when you want to have statistics over many users.

[ Parent | on HN ]

Re:Pocketbase: Open-source back end in one file by rudasn on Sunday January 07, 2024 @07:37AM (#38900742)

I'm in this situation right now. How would one go about solving this?

To keep this simple, I'm thinking exporting just the necessary data from each db and inserting that to a stats db (having a source column to each table, referring to the original db). Then load the stats db with Metabase or something.

Migrations on the stats db may be a bit of a pain, as well as making sure that all data is exported and imported correctly every time.

I'm sure there are better ideas.

[ Parent | on HN ]

Re:Pocketbase: Open-source back end in one file by jocaal on Sunday January 07, 2024 @07:47AM (#38900786)

Litestream is a library that allows you to easily create backups. You can probably just do analytics queries on the backup data.

https://litestream.io/

[ Parent | on HN ]

Re:Pocketbase: Open-source back end in one file by djfobbz on Sunday January 07, 2024 @11:36AM (#38902581)

See this: https://news.ycombinator.com/item?id=26581807

[ Parent | on HN ]