All articles

Which to choose, the expressive power of code, or the robustness of built-in database features? With Convex, you can have both. By eliminating the boundary between the application and the database, Convex provides a uniform and powerful way to model your entire backend data flow and security using plain ol' code.

This post will cover various aspects of operational maturity, and steps to take as your app grows up.

Read this article to learn how you can build our open-source backend from source.

Before you burden yourself with “best practices” for large-scale companies, focus on what will reduce your feedback cycles and help you ship early and often. Think about your use case, not your toolbox.

Patch all of your data in your database table with the bulk edit feature on the Convex dashboard, without writing migration code.

I recently built a full-stack app called notesGPT. It allows you to record a voice note, transcribes it, and extract action items and display them as action items. It’s fully open source and comes equipped with authentication, storage, vector search, action items, and is fully responsive on mobile for ease of use.

Convex Ents is a library that provides: simpler ways to model and query related documents, ability to easily map and filter documents, enforcing unique field values, default field values, cascading deletes, soft deletion and more!

Traverse database relationships in a readable, predictable, and debuggable way. Support for one-to-one, one-to-many, and many-to-many via utility functions available in convex-helpers.

Re-use code and centralize request handler definitions with discoverability and type safety and without the indirection of middleware or nesting of wrappers. Use the new customFunction module in convex-helpers for your Convex TypeScript functions.

Does your app need to limit the amount of users that can use it at a time? You might need to add a waitlist, which you will learn to build in this post.

Convex is a full-stack development platform and cloud database, including built-in vector search. In this third post in our [series](https://stack.convex.dev/ai-chat-using-openai-assistants-api), we’ll build an AI-powered chat interface using Convex, with our own message storage and context retrieval.

Learn how you can win cash prizes for building features on an open-source Notion clone.

Launching our official Convex Fivetran connector.

Learn more about how AI Town works and how to customize it. In this post, we'll dig into how character identities are represented: how to alter them, and how to add entirely new characters.

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

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.

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.

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

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.

An approach to server-persisted session data with Convex, wrapping your server functions and storing a session ID on the client.

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.