All articles

Let's build a full-stack chat app to talk to ChatGPT on its new API!

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

There are as many ways to migrate data as there are databases, but here’s some basic information to set the stage.

In this post, we’ll look at how to use the moderation API to flag messages before sending them to Chat-GPT, and patterns for handling these errors in a full-stack React app.

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.

Use Convex to fetch an image from OpenAI’s image generation service based on a user-provided prompt.

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.

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.

When your database supports ACID semantics, you're free to write code the intuitive way and ignore the complexities of concurrency and failure.

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

The serverless movement has eliminated so many problems but it has left application developers with the hardest one of all: managing distributed state.

You don’t have to worry about the platform locking you into a decision that seems convenient at first but is a headache to deal with later.

Relational databases are powerful tools for persisting data, but using them to build interactive web apps requires a lot of work. A web app architecture built on a relational database is an entire cluster of databases, backends, caching nodes, and Pub/Sub servers. And even after you invest in all of that infrastructure you'll still need to explicitly define your database schema upfront and write cumbersome SQL queries. At Convex we believe that web developers shouldn't have to worry about any of this. We can handle the servers, caching, and reactivity and you can focus on your product.