Spending $5k to learn how database indexes work
briananglin.me
Spending $5k to learn how database indexes work
1–10 of 209 posts
Re: Spending $5k to learn how database indexes work
#20,15 $ per query... The world has gone insane.
Re: Spending $5k to learn how database indexes work
#3Huh, learning about this "Superwall" product constitutes as my horror-story-of-the-day. It's paywalling as a service, just what the industry needed. Thankfully it appears to be quarantined to iOS right now, but God does it feel like we're headed right back into Stallman's predictions about how SAASS will ruin the landscape of commercial technology.
Re: Spending $5k to learn how database indexes work
#4Huh, learning about this "Superwall" product constitutes as my horror-story-of-the-day. It's paywalling as a service, just what the industry needed. Thankfully it appears to be quarantined to iOS right now, but God does it feel like we're headed right back into Stallman's predictions about how SAASS will ruin the landscape of commercial technology.
Two sides to every coin. Ethical developers need ways to make low prices work, which is impossible without good testing suites.
Re: Spending $5k to learn how database indexes work
#5Gotta love cloud pricing. This is why I colocate.
Re: Spending $5k to learn how database indexes work
#60,15 $ per query... The world has gone insane.
It's not quite so crazy when you phrase it as $0.15 for reading a million items from the database.
Re: Spending $5k to learn how database indexes work
#7Re: Spending $5k to learn how database indexes work
#8Re: Spending $5k to learn how database indexes work
#9I'm not a DB expert, but "750k users in a month." doesn't sound like a quantity that you'd need to use some kind of fancy special tooling for.
Re: Spending $5k to learn how database indexes work
#10No foreign keys to make migrations easier. That doesn't sound like the best trade off to me.
Having the database constrained as much as possible makes maintenance so much easier. Many bugs don't escape into production as they're caught by the database constraints. Those that do get out do less damage to the data.
I know scale comes with trade offs but that seems extreme to me.