My understanding was that "you can't use SQLite in production" was always just a shorthand for "SQLite doesn't support concurrent writes". Obviously still works well in a lot of production application contexts.
The default compilation for SQLite is backwards compatible to all prior versions. With compilation flags, SQLite is a bit more robust. Like a lot of other technologies, we've brought forward our past understanding that obscures current capabilities.
My understanding was that "you can't use SQLite in production" was always just a shorthand for "SQLite doesn't support concurrent writes". Obviously still works well in a lot of production application contexts.
The default compilation for SQLite is backwards compatible to all prior versions. With compilation flags, SQLite is a bit more robust. Like a lot of other technologies, we've brought forward our past understanding that obscures current capabilities.
Really good talk. The latency measurements at 30:00 are crazy impressive, SQLite blows Postgres away.
they told me "you can’t use SQLite in production ..."
😂
great presentation, thank you! I will use go and sqlite for my next project
HAHHA tailscale did move their working database to sqlite!
This is a great presentation, thanks for sharing
Excellent. Thanks.
thank you michael keaton
SQLite does my job well, Thanks
I have a question? Are you one of a guy who are developing Pocketbase?
500 microseconds is not half a second.
its half a millisecond.
at the beginning you show the configs. How do you set them when using sqlite from go? You put them in ~/.sqliterc ?