@convex.dev now has an MCP server! the cursor AI agent can now list project's schema and API, read data from tables, and call functions.

it's insane how good it is at gluing tool calls together. here's an example of it building a histogram of a message lengths in a chat app.

we looked at zanzibar yesterday, where a user A has access to an object B if there's a path between them in the access graph. let's walk through how they make this graph reachability problem efficient.

then, each (object, relationship) pair gets a node too. let's say we have one group and two documents. groups have admins and members, and documents have owners, writers, commenters, and readers. I've drawn a dotted line connecting these nodes to their shared document for clarity.

we start by filling in a red node for our user. each user gets one of these nodes in the graph.

authorization comes up a lot, and it's easy to get lost in the soup of different ways to express who can access what (ACLs, RBAC, ABAC, ...)

we've been working on @convex.dev for almost four years now, and it's an incredible feeling to see the first *book* on using convex out there 🤯

reactive UIs, build systems, and materialized views in databases are all flavors of incremental computation.

jamie brandon has an excellent analysis of incremental systems across three dimensions: structure, temporal locaity, and consistency.

amazing work from @convex.dev engineer ian maccartney wiring up automerge to convex!

reminds me of PDO grading for balsamic vinegar

"quiver" -> "sub-simmer" -> "simmer" -> "boil" -> "roiling boil"

we've long held at convex that SQL isn't a great fit for OLTP workloads. buuuuut, with all of the recent SQLite WASM work, why not try stuffing it into a convex component?

and while we're at it, did we just get reactive SQL queries for free?

(crosspost from the other place)