Convex

ok we finally did it 🇪🇺

Convex @convex is an absolute game changer for people spinning up a bunch of AI prototypes with a backend requirement. Free tier is unbelievably generous too. Migrating everything over. (h/t @theo for the recommendation)

It's that time. This week in @convex. A look at what people are building.

M.A.U. Podcast by Convex x.com/i/broadcasts/1…

Excited for today's M.A.U. podcast by @convex with special guest: Catherine Jue @juecd__ co-founder of @usekernel Adi Singh @adisingh co-founder of @agentmail Cohosted with @Rasmic @jamwt

Woo! My biggest contribution to @convex so far has just been accepted and merged in. This one auto-injects more AI intelligence into your convex projects via guidelines and skills. Ill do a proper video on this once it lands in the CLI.

@existentializzm @mikeysee goals

@convex @mikeysee Convex is turning into buzzfeed now? "number 7 will shock you!"

the slop is starting to really slop out there. @mikeysee wonders: can the code review bots like coderabbit and greptile save us?

you should watch the whole thing youtube.com/watch?v=JmraS2…

finally: visit our office and prove you are the GOAT nerd

Wait… I’m actually obsessed with Codex + GPT-5.4 🤯 Built a Club Penguin clone in 6 prompts. Then used @convex to make it multiplayer. Didn’t expect this but… @OpenAI might've officially converted me to Codex for vibe-coding.

carried by @mikeysee

always rated @GeminiApp

This week in @convex. A look at what people are building.

M.A.U. by Convex x.com/i/broadcasts/1…

if you want one, here they are store.convex.dev/en-usd/product… (all profits donated to OSS)

WHAT did the convex "swag team" just— ughhh, it's 🔥 from @existentializzm

Convex had downtime for some customers this morning, caused by an "anomalous load spike" that pushed an internal service into a load-shedding mode, which then triggered an unexpected panic in a caching library we were using. Specifically the load triggered two queue management algorithms: CoDel which proactively drops requests to keep queues small, and adaptive-LIFO which dequeues in reverse order to avoid wasting time on old requests. These are both rather subtle algorithms that large services use to avoid congestion collapse under high load or attack. The panic in the caching library was just a bug that depended on both these algorithms simultaneously. We've made some changes as a result of this incident but the key lesson is that services should try to avoid switching logical behavior during high load. When systems are stressed switching to infrequently-used codepaths can often make matters worse. We're now going to be proactively triggering CoDel and adaptive-LIFO at steady state to ensure that we're exercising this worst-case flow at all times. Distributed systems are hard and our team is typically excellent at this kind of work, but sometimes problems happen and give us an opportunity to harden our systems. We're sorry about the negative impact for those affected!

I made a video demystifying database consistency, isolation levels, record contention, and pessimistic vs. optimistic concurrency control tradeoffs. (I also said "dollars" instead of "pounds" 40 times.) Check it out if you want a basic working knowledge of this stuff.

congrats to the drizzle team massive respect to a fellow traveler on the journey to make databases suck less