Mike Coutermarsh
@mscccc
Followers
11K
Following
165K
Media
1K
Statuses
19K
Building really fucking fast MySQL and Postgres databases @PlanetScale
Pennsylvania, USA
Joined December 2009
Blogged about our DB migration to @PlanetScale. We moved about a month ago and it's been great. Insights is the best feature. https://t.co/wMBHtVGx09
getsupernova.ai
We moved our Postgres DB to PlanetScale Metal to cut latency and gain real query visibility—our app is noticeably faster.
2
8
39
7yr-old: you know what I hate? Me: don’t say hate buddy, say really don’t like 7: ok, you know what I really don’t like? Day light saving Me: oh never mind you can hate that 7: ok good
1
2
24
What do Andrew Atkinson, me, and @mscccc all have in common? We don't let our friends use UUIDv4 as primary keys.
4
4
52
I love these scaled stories Netflix - 5PB per day, 10m events per second. ClickHouse 🐐 https://t.co/XS9cYiA2RH
clickhouse.com
“To make our logging system work, we had to make a lot of choices. The key is how you simplify things in order to do the least amount of work.” Daniel Muino, Software Engineer
Everyone including PlanetScale seems to use Clickhouse.
8
23
465
shipped.
Hey @PlanetScale team. It would be cool if you could add a "copy summary" button to the insights table (or individual view) that gives a good summary of the proposed change that I can paste straight into an LLM and get it to review the impact of the change in the context of my
2
4
111
I benchmarked 96 combinations of Postgres 17 and 18. There's a few surprising results, but overall Postgres 18 has some nice improvements. Read all about it at the link below.
5
16
127
Ok GitHub that's nice. new merge conflict UI. Current change/incoming change is nice naming as well.
2
0
25
I tried to explain why I don't believe the recent accusations toward my former teammates, as well as how the Ruby and Rails Infra team at Shopify operates and why it can be trusted. https://t.co/cgRySjoVlr
byroot.github.io
I’ve been meaning to write a post about my perspective on Open Source and corporate entities. I already got the rough outline of it; however, I’m suffering from writer’s block, but more importantly,...
17
65
328
If your instinct is to argue with this tweet, you’d hate working with me
Correctness, clean code, DRY, abstraction purity - the shibboleths of people who get nothing done
7
2
98
Sharded Postgres, incoming.
Neki - Vitess for Postgres, lives. These are sharded Postgres queries.
3
0
59
Neki - Vitess for Postgres, lives. These are sharded Postgres queries.
15
26
318
Most takes about ORM performance I see online are way off base. I hear about abstraction overhead (very unlikely to matter in practice) and sub-optimal queries (also quite rare, because database query planners are very good these days). The main way an ORM is going to nuke your
5
14
166
Welcome to the public_id club! A place for classy applications. No uuid slop here.
Thinking of using UUIDs for public facing + tenant IDs, but they feel a bit long and messy. Came across this great blog post by @PlanetScale on NanoIDs super insightful! I’m literally adopting their config 🔗
4
0
19
My life is fun
Just shipped: we've partnered with PlanetScale to make deploying full-stack, database-backed apps using Workers + PlanetScale Postgres (or Vitess!) really, really easy. Link your accounts, create a config, and deploy an app that can scale to millions of QPS without having to
4
2
133
fast databases 🤝 fast global apps it's been hella sick working with @mscccc and team on this, the PlanetScale team knows how to ship 🔥
just shipped: link your Cloudflare & @PlanetScale accounts + connect Workers to your Postgres or Vitess databases in a couple of clicks.
1
1
12
just shipped: link your Cloudflare & @PlanetScale accounts + connect Workers to your Postgres or Vitess databases in a couple of clicks.
Better @Cloudflare integration
6
17
132
Used @jsneedles 's @htmlcsstoimage to automatically create standardized opengraph / Twitter card images for my 160+ back catalog of personal blog posts - was pretty easy to configure with Jekyll. Works great! Should I do a write-up on how to do it?
3
3
24