Been using SQLite for many years now... It's simple, just a file, portable and does most things a more fancy database will do for you... I'm a big believer on start simple and keep it that way until you have to go more advanced... Nice talk, I'm enjoying it
Kudos to CJ. Give him more juice! He asked really tough, important questions and got hand-wavey, word-salad answers. I think he was a bit intimidated and he shouldn't have been. I am a huge fan of Syntax and think they generally do great job--but this episode was mostly a marketing-heavy promo.
Sorry to hear you felt it was marketing heavy. I (Scott) was genuinely stoked to hear about the sqlite syncing as a core feature, not because it's a product on the show, but because I've been in that space for a bit and it's tough to find anything turn key here. CJ def rules though, he's the man.
Agreed! I understand guests may not want to have to compare their product to existing competitors in the domain but doing so really gives us an understanding of the product. Those question(s) in particular were awesome.
Then you don't understand anything about SQLite, because it's obvious why MySQL was chosen for web on production and not SQLite: SQLite didn't even add WAL mode until 2010 and it's only gotten reasonable recently. The rollback journal was completely impractical for multi-user applications for even the simplest of applications.
How do we run migrations when we have a large number of instances ? Wont we end up in a state where some migrated and some not depending on the network connectivity?
Sqlite is a amazing database for smaller project but in terms for production ready application sqlite left behind because of its single concurrent write operation and can't be scaled :/ recently turso has extend sqlite for production with libsql. Not yet tried, will try soon maybe
@@weiSane turso's free tier looks promising for small projects, but there is no such backup facilities for free tier. Atleast I didn't find any information about db backup on the free tier. Paid tier has backup facilities but i prefer to spend those penny's to host own postgres
Sqlite is plenty enough for “production,” depending on the characteristics of your workload. It’s been used in literally in tens of thousands of production applications. Turso and libsql have the same limitations, if you need more than 10k transactions per second then you may need something faster, but you also probably have more tables than paying customers. It seems like you don’t really understand what you’re saying, you’re more likely parrroting from something you think you heard somewhere. Presenting yourself as an authority, no less. Lurk more.
@@JeremyAndersonBoise lol who’s presenting themselves as an authority? We are literally just discussing something that seems abit intriguing and no one said sql doesn’t have its weak points and we all contended that for some applications it’s not not the right choice and there are good replacements for it in those scenarios like Postgres etc . So again, who’s lurking and who’s being an authority in this SQLite discussion? Pathetic.
Been using SQLite for many years now... It's simple, just a file, portable and does most things a more fancy database will do for you...
I'm a big believer on start simple and keep it that way until you have to go more advanced...
Nice talk, I'm enjoying it
Good philosophy
Love the Sqlite renaissance in recent months! Awesome episode 🎉
Kudos to CJ. Give him more juice! He asked really tough, important questions and got hand-wavey, word-salad answers. I think he was a bit intimidated and he shouldn't have been. I am a huge fan of Syntax and think they generally do great job--but this episode was mostly a marketing-heavy promo.
Sorry to hear you felt it was marketing heavy. I (Scott) was genuinely stoked to hear about the sqlite syncing as a core feature, not because it's a product on the show, but because I've been in that space for a bit and it's tough to find anything turn key here. CJ def rules though, he's the man.
@@syntaxfm Thanks for the reply, Scott.
Agreed! I understand guests may not want to have to compare their product to existing competitors in the domain but doing so really gives us an understanding of the product. Those question(s) in particular were awesome.
sqlite makes sense for most websites, kinda surprised mysql dominated the general website landscape for so long
Then you don't understand anything about SQLite, because it's obvious why MySQL was chosen for web on production and not SQLite: SQLite didn't even add WAL mode until 2010 and it's only gotten reasonable recently.
The rollback journal was completely impractical for multi-user applications for even the simplest of applications.
I have huge respect for both of these guys. SQLite is definitely something I'm turning focus towards.
How do we run migrations when we have a large number of instances ? Wont we end up in a state where some migrated and some not depending on the network connectivity?
Congratulations, CJ! 🥳 I didn't know that you had a new baby.
Sqlite is a amazing database for smaller project but in terms for production ready application sqlite left behind because of its single concurrent write operation and can't be scaled :/ recently turso has extend sqlite for production with libsql. Not yet tried, will try soon maybe
torso and libsql by itself is a game changer. But I don’t want the stress of managing it all by myself so I use turso
@@weiSane turso's free tier looks promising for small projects, but there is no such backup facilities for free tier. Atleast I didn't find any information about db backup on the free tier. Paid tier has backup facilities but i prefer to spend those penny's to host own postgres
Sqlite is plenty enough for “production,” depending on the characteristics of your workload. It’s been used in literally in tens of thousands of production applications. Turso and libsql have the same limitations, if you need more than 10k transactions per second then you may need something faster, but you also probably have more tables than paying customers. It seems like you don’t really understand what you’re saying, you’re more likely parrroting from something you think you heard somewhere. Presenting yourself as an authority, no less. Lurk more.
@@JeremyAndersonBoise lol who’s presenting themselves as an authority?
We are literally just discussing something that seems abit intriguing and no one said sql doesn’t have its weak points and we all contended that for some applications it’s not not the right choice and there are good replacements for it in those scenarios like Postgres etc .
So again, who’s lurking and who’s being an authority in this SQLite discussion?
Pathetic.
sqlite for the win! most apps are not corpo nor unicorns, lets light that lite!
SQLite is pronounced either "Es-Ku-El-Ite" or "See-Kwe-Lite". It has never been pronounced "Es-Ku-Lite" until this podcast :)
Prove it! 😂
Assy-Keh-Lite I prefer
As a Minnesotan, Brian's background was a nice little easter egg 😂
IDS!
Yoo, CJ here
CJ will be on a ton of episodes this month as Wes is on paternity leave