Databases episode 3
:mind_blown_wow: Wake up babe! 🥱
New episode of Databased just dropped. https://www.youtube.com/watch?v=WjIbppFX7Ww Find out why you secretly hate SQL.
New episode of Databased just dropped. https://www.youtube.com/watch?v=WjIbppFX7Ww Find out why you secretly hate SQL.
Convex
YouTube
Scaling SQL Databases for Modern Applications
In this episode of Databased, Tom Redman speaks with Jamie Turner and James Cowling about the historical context that necessitated the invention of SQL 1.0 and how these databases have scaled over time. They touch on the challenges of maintaining transactionality and consistency, the rise and limitations of NoSQL databases, and optimizing for de...
9 Replies
Every episode blows my mind-about one year ago I learned about convex. For less than 6 months I’ve been using it a lot. I can do full stack development quicker than I could just do back end development after 20 years of experience
It can hurt your brain because it’s just so much power at your finger tips
The future is here
Also the intro music slaps more than it has any right to
thanks so much for the kind words
honestly, after 20+ years of backend experience, I can also get stuff done faster with convex than without it! so glad to hear others feel the same way
even all those at convex, who built it, have the most fun and get stuff done fastest when we're using it. in fact, there are hot debates internally about how much of the software the company needs we can use convex to make. most engineers push to use it as often as possible 🙂
Very curious how and why both Postgres and MySQL are used
we use postgresql for our accounts database, but mysql is the rdbms that underlies convex projects right now. they're fairly interchangeable though. each has pros and cons.
we might move back to 100% postgres at some point, but no hurry on that.
Is there an article on the pros and cons
dunno, maybe we can write one. but in general I would recommend people use postgres
just like solid.js is actually better than react... unfortunately it doesn't matter that much. the ecosystem power is a monster.
the postgres situation is the same way right now
things like RDS etc, they're investing way more heavily in the postgres offering b/c it's cool right now
so that becomes kind of self-fulfilling
I was a postgres fan in '98 and thought MySQL was a joke... then worked at a bunch of mysql shops in mysql's heyday and realized how much google/facebook & co had beaten that thing into submission for production -- it was the "devil you know", and postgres was a joke at scale. now postgres is back the rage again, the last 5-7 years, and so mysql momentum, ecosystem, & platform investment has slowed down. probably wise to ride the wave when it comes to RDBMSes, b/c there's nothing terribly distinguishing about their feature sets to otherwise set them apart IMO. great platform support and healthy ecosystem matters the most
and thought MySQL was a jokegranted this was like the MyISAM days when MySQL didn't even have transactions. I will also call out that our team has had to work really hard and become quite expert with both MySQL and Postgres to make them actually (a) perform consistently well and (b) have actual sound, consistent relationships to their records and truly follow ACID. it's not trivial. I would guess most databases in the wild are a little broken and people mostly don't notice. the out of the box usage of these databases is not set up for success
My mantra is “just use convex” I don’t think anything else can compete. I think it’s a complete solution in the backend. Until another product basically tries to copy your approach completely I feel very comfortable being totally bought in on convex
That still leaves so many decisions to make on the front end. I am much less clear on the trade offs to different front end solutions
I built a project based on the monorepo template. I just went through the process of converting my next.js website to vite so I could get convex auth working on the web and on native react.
I would love some direction on evaluating all the different front end options. Until I built the vite website I didn’t realize that next.js is running some of the code in the server side at run time
Also curious about your road map for supporting all the different front end ecosystems
when we release support for tanstack start, that will probably become our recommended fe framework
my prediction is tanstack + convex will be the best all-around full stack choice at that point
Interesting I’d never even heard of tanstack before Convex started talking about it