Patterns

Learn how to generate fake data for your dev deployments using the Faker library

Pinecone and Convex are a good match when you're looking to build an application that leverages embeddings and also has application data.

Embeddings, why they’re useful, and how we can store and use them in Convex.

Implementing row-level security on Convex as a library. Wrap access to the database with access checks written in plain old JS / TS.

In this post, we’ll look at some helper functions to help write code to traverse relationships in a readable, predictable, and debuggable way.

Using mutations to migrate data in Convex.

Your document is safely stored, but search is coming up empty? Inconsistent search systems can really confuse users! Don't worry–in Convex, transactional search indexing ensures that users always get what they expect and your apps just work.

Adding advanced HTTP Endpoint functionality by extending Convex with Hono.

Reactive backends like Convex make building live-updating apps a cinch, but default behavior might be too reactive for some use cases. Not to worry! Let’s fine-tune the reactive dataflow of a Convex + React app to deliver a better UX.

Implement asynchronous job patterns using a table to track progress. Fire-and-forget, cancelation, timeouts, and more.

Getting users to sign up for a new service before seeing any benefits is challenging. In this post, we looked at a couple of strategies for managing user information without requiring a login.

How to implement session storage with Convex, using some helper functions we wrote. While most of your data is associated with a user or another document, sometimes you have data that is specific to a user’s browser tab, or associated with a user who isn’t logged in. Some of this data is stored on the client, such as in the browser’s `sessionStorage` or `localStorage`, while other data is stored on the server.

Function validation is important for a production app because you can’t always control which clients are talking to your server. See how to use zod to validate your Convex functions, using our withZod wrapper.

Convex middleware serves many purposes. Sometimes authentication, sometimes i18n. This time? Making sense (or nonsense) of emerging technology industry trends.

Using wrapper functions like withUser can help you organize your code into middleware-like blocks that you can compose to keep your function logic concise.

Some patterns for incorporating presence into a web app leveraging Convex, and sharing some tips & utilities I built along the way.

For write-heavy applications, use single flighting to dynamically throttle requests. See how we implement this with React hooks for Convex.

Today we’re going to talk about how to flip features on and off remotely using a clever use of the reactive nature of Convex queries.

Reactivity has taken a dominant position today within web app development. Our components and app state are all reactive, and the world has adapted–most would argue, for the better. But has Convex gone too far? 😉 A new generation of serverless backends like Convex is recklessly spreading reactivity across our databases, server-side functions, and protocols, making global reactivity a new phenomenon. Shared global data is becoming reactive by default. Is this good for the world? In this video, Jamie Turner explores one circumstance where this pervasive reactivity poses a challenge, and he builds one useful abstraction for taming over-reactivity and turning it back into a strength.