Why I use Convex over Supabase as my BaaS

TL;DR

A detailed comparison of Convex and Supabase for real-time databases, highlighting pros and cons.

Transcript

I made a video about four weeks ago where I talked about how I'm switching from post grass to a real-time database called convex and I got a lot of questions asking about a service called superbase so I spent some time basically comparing superbase against convex and I want to give you the pros and cons in my opinions on why I decide to choose conv... Read More

Key Insights

• ⌛ Convex provides a more developer-friendly interface with better type safety and real-time capabilities compared to Supabase, which relies heavily on SQL.
• 💄 Supabase simplifies setup with readily available templates and integrated authentication, making it accessible for quick project initiation.
• 👻 Convex’s approach to backend logic allows developers to avoid direct database manipulation, achieving better separation of frontend and backend concerns.
• 👨‍🔬 Both platforms feature capabilities for vector search, showing their alignment with modern application needs like AI integrations.
• 🖤 Local development support is a strength for Supabase, which can run entirely in Docker, whereas Convex lacks local testing capabilities, potentially challenging some workflows.
• ⚾ Migrations in Supabase align closely with traditional SQL operations, while Convex offers TypeScript-based migrations, fostering familiarity for developers already within that ecosystem.
• 👻 Supabase's need for SQL expertise creates a steeper learning curve, contrasting with Convex, which allows developers to operate primarily within TypeScript and React environments.

Questions & Answers

Q: What are the primary advantages of using Convex over Supabase?

Convex offers several advantages, including superior type safety and a seamless developer experience with automatic type generation. The paradigm where all functions are predefined on the backend allows for better abstraction and separation of concerns. Moreover, its real-time capabilities require less manual setup, which benefits developers looking for efficiency.

Q: How do the authentication systems of both platforms differ?

Supabase has built-in authentication features, offering easy-to-implement user sign-up, password resets, and social login options directly within its structure. In contrast, Convex recommends using third-party authentication services like Clerk, which may require extra setup and customization, making it less integrated out of the box.

Q: What challenges arise when using Supabase regarding SQL knowledge?

Users of Supabase often find themselves needing a deep understanding of SQL, as many features, such as row-level security and custom policies, require writing SQL commands. This can be a significant hurdle for developers who prefer to focus on application logic rather than learning SQL intricacies.

Q: How does data storage and file handling differ between Convex and Supabase?

Supabase allows file uploads through a simple UI integrated with its PostgreSQL backend, which is easy to manage. Conversely, Convex requires writing mutations to generate signed URLs for file uploads, adding an extra step but maintaining seamless integration once set up. Both systems manage storage efficiently, catering to user needs.

Q: What is the developer experience like when using Convex compared to Supabase?

The developer experience in Convex is generally reported as superior, thanks to its automatic type generation, streamlined processes, and a coherent framework that integrates with frameworks like React. In comparison, Supabase can feel cumbersome due to its reliance on manual SQL adjustments and the need for deeper database knowledge.

Q: Can you explain how real-time updates are handled in both technologies?

In Supabase, real-time updates necessitate manual subscriptions to database events, requiring more code for effective data handling. However, Convex automates this process, where any data changes trigger automatic updates in the UI without additional coding, making real-time integration simpler and more efficient.

Summary & Key Takeaways

• The video is centered on a comparison between Convex and Supabase, focusing on their configurations, paradigms, and features for building web applications. The presenter shares insights from a project called "Meme Ranker" using both technologies to underline the differences.

• Convex is praised for its type safety, built-in real-time capabilities, and better developer experience, whereas Supabase is recognized for its easy setup and integrated authentication features using PostgreSQL as the backend.

• Key aspects such as setup, paradigms, schema management, real-time functionality, and developer experience are examined, ultimately advocating for Convex due to its efficiency and ease of use.