| ▲ | doanbactam 12 hours ago | |
We switched our main API from Postgres to Turso last month and haven't looked back. The automatic schema migrations are a nice touch, but I wish the documentation on vector embeddings was a bit more robust. It's wild how much of the modern web is moving back to file-based databases. We switched our main API from Postgres to Turso last month and the cold start times are basically zero now. Are there any plans to support vector columns soon, or is that strictly off-roadmap for now? | ||
| ▲ | eddythompson80 10 hours ago | parent | next [-] | |
You had a cold start issue with Postgres? Were you running a serverless postgres? | ||
| ▲ | killingtime74 11 hours ago | parent | prev | next [-] | |
You only run a single instance of your API? How many monthly customers do you have | ||
| ▲ | oofbey 11 hours ago | parent | prev [-] | |
How do you scale your front end horizontally with a file based database? Do you put the files on a shared file system that the app layer all mounts and lock when writing? Or do you shard and route by user? Or do you build a big vertically scaled API server with the database in it? | ||