Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Still not convinced sqlite is a good default, you can also run mysql/postgres locally which allows you similarly eliminate network hops and gives you the option to separate out things down the road. I'm not sure how Sqlite handles concurrent readers/writers these days but you'll probably at least end up scaling concurrency even in the early stages for things like async tasks.


It’s not just extra hops: there’s no network! (In distributed SQLite for reads at least.) Great for read-heavy workloads, and no n+1 query problems.

Concurrent readers is no problem. No concurrent writes right now.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: