Convex

convex for enterprise is here. lawyers, rejoice news.convex.dev/enterprise-lau…

convex durable functions kit gets stronger and stronger every day. gg @ianmacartney and huge updates for massive scale and lower costs coming in the second half of 2026

the boys are back with another databased episode, check it out to hear some hot takes on systems design youtu.be/Ba_qaUtAvGM

your backend doesn't know what's best for you if it's letting you run full table scans

M.A.U. by @Convex with Micky and Jamie - What Models? x.com/i/broadcasts/1…

@potencytoact @AnthropicAI guidelines often need a bit of tweaking for new models. it's stronger out of the box, which is probably the purest measurement

@convex @AnthropicAI Shouldn’t it be better than 4.6?

aye @AnthropicAI ate on this one

Using @convex for my backend and the function logic is the most relaxing thing I have done today. Fantastic tool.

🦀 East Bay Rust comes to SF hosted at @Convex x.com/i/broadcasts/1…

rust >>> zig come argue with us tonight

@OmarMcAdam @jamesacowling secretive

@jamesacowling Hows @convex feeling on this?

Welcome to the era of secrecy! Expect to see a lot of folks reconsidering having their source code in the wild, especially their tests.

read up on the release, and tell us what you want next: ship.convex.dev/changelog/conv…

🛳️ convex 1.35 shipped—featuring many ergonomic improvements for agentic engineering, like support for multiple, parallel dev environments, temporary deployments, etc. and 642 convex chips just yielded returns to convex developers who bid on these features.

@leodev @tebayoso if you know you know 🤜🤛

@convex @tebayoso Yea but it won't hurt to use convex x.com/i/status/20422…

@leodev @tebayoso We’re not a Postgres hosting provider.

@convex @tebayoso what about "just use convex?"

Time for a big systems advice thread! In distributed systems there's no magic "push everything to prod at once" button. Every service gets pushed independently and nodes within a service get updated incrementally. If you mess up forwards/backwards compatibility you can fail irrecoverably. So how to avoid this? 1/5: Decouple data and code changes. Never push out a release that changes how data is stored at the same time as the code that uses this new data. If there's a bug and you need to roll back to the old version of your code it won't be able to handle the new data in the new format. Instead push out a release that first changes the data in a way that’s compatible with both the old and new code (e.g., optional fields etc), when that’s stable push out the new code that uses it, then when that’s stable you can change the data to remove backwards compatibility. This is known as a “migration” in the database world and yes it’s annoying, but yes you need to do it.

uncut: youtube.com/watch?v=eelTID…

yc hackathon had a visit from @Rasmic @waynesutton @magicseth to see all the convex builds some scouring for yc investment checks lying around may have happened. easiest way into the batch?

I love postgres But I had to switch back to convex... I just start missing all of @convex's realtime features 😭

@hexwanderer we're hiring a head of product. you are now shortlisted

@convex Have you considered using the number of o’s to distinguish how much RAM To allocate? use node > 5MB use noooode > 20MB

convex 2.0 has been online internally since february. when first activated, it synced data that didn't even exist yet in response, we've made a "convex lens" program with select partners. a think tank to prepare the world for this level of DX if you're not scared, you're ngmi