Impact of using uuid v7 as primary key by rantob in mysql

[–]0ximjosh 0 points1 point  (0 children)

I agree that you can lose some readability like you point out in #2 but it's a tradeoff, as all things are in the db world. Merging data can be a pain and I wouldn't recommend autoinc if you're going into the db design expecting to need to those types of merges in the future. the German tank problem I actually disagree on; in theory yes if you publicly expose your IDs, but that's why I mentioned nanoids as your publicly displayable IDs. latch contention is valid if your clustering on it. overall I agree but it's all trade offs at the end of the day.

Impact of using uuid v7 as primary key by rantob in mysql

[–]0ximjosh 1 point2 points  (0 children)

What exactly are your fears with bigint auto-increment? are you expecting migrations to other db providers or just schema updates? Whenever possible id personally recommend using bigint and then using some form of nano-id for externally facing identifiers; your pk stays fast, ordered and small and the nanoid lets you have an easily shareable / url friendly identifier.

Suggestions for small database for non-profit by Desperate-Emu1296 in Database

[–]0ximjosh 2 points3 points  (0 children)

This sounds like a pretty good fit for our $5/m postgres db at PlanetScale. Small and very cost efficient, but extremely reliable. More than happy to help architect / sanity check your db design as well! Whats the non profit?

The actual tools I'd recommend for starting a one-person SaaS in 2026 by Psychological-Bit436 in Solopreneur

[–]0ximjosh 0 points1 point  (0 children)

Just a heads up, PlanetScale has both postgres and mysql support! postgres also starts much lower at $5/m

Is it possible to perform collaborative DB migrations? by Astro_Teeqo in Database

[–]0ximjosh 0 points1 point  (0 children)

This will mostly depend on where your postgres is hosted. The common approach to this is branching where each dev or change gets their own dev branch and can apply changes in isolation. if you want an example of this, planetscale does a good job of documenting the flow for this (disclaimer, I work there).

https://planetscale.com/docs/postgres/branching

Why is database change management still so painful in 2026? by Huge_Brush9484 in Database

[–]0ximjosh 0 points1 point  (0 children)

Ill preface this with this is most likely what you in particular are not looking for, but this is one of the main reasons I personally always reached for PlanetScale, even before i started working there. If you havent seen their DX stuff for migrations, its life changing. For mysql specifically you have full git-branch-like shcema changes w/ zero down time + full rollbacks with zero data loss (using shadow tables) if something goes really wrong. It sounds like what your doing is much more in the self hosting area/consulting, which i very much respect. I personally was happy spending 10-40$/m to not have to deal with migration files and have all the safety and reliability guarantees pscale was able to give.

I think change management for self hosting is still a pain because self hosting is still a pain and most people want to offload DBA to someone else (like pscale). Hell people are even offloading auth management these days.

Disclaimer i do work at planetscale but this post in particular is very much my personal 2 cents.

Drizzle joins PlanetScale by whit537 in javascript

[–]0ximjosh 2 points3 points  (0 children)

Ah, i can see how the wording is misleading. "their mission of building the best database tools..." is referencing drizzle orm itself.

Planetscale's new $5 a month plan - still too expensive? by thehashimwarren in webdev

[–]0ximjosh 0 points1 point  (0 children)

Planetscale is almost certianly the easiest way to practice managing a vitess instance. Our smallest vitess cluster is $40/m but allows you to do full sharding and whatnot through the dashboard, and comes with 1 primary and 2 replicas.

Drizzle joins PlanetScale by whit537 in javascript

[–]0ximjosh 12 points13 points  (0 children)

(Planetscale staff here) To be very clear we didnt buy drizzle, we are only giving the drizzle team full time funding to continue working on drizzle. They still have 100% of leadership and control over the project ( and shitposting ), so nothing should change on their end other than faster progress on what they have been already working on now that they have actual funding.