EdgeDB

EdgeDB — next-generation object-relational database on PostgreSQL.

DatabaseComplex

Stack Components

DatabaseEdgeDB 5.x

BasePostgreSQL

Why

Object-relational model, EdgeQL with computed properties, migrations, and links. PostgreSQL is used by nearly 50% of professional developers, making it the most popular database (Stack Overflow 2024).

SQLite powers 1 trillion+ active databases (every iOS/Android device), and DuckDB emerged as the fastest OLAP engine for analytics, 5-10x faster than ClickHouse for single-node queries.

When

Use for apps wanting ORM-like DX on PostgreSQL. Avoid for existing SQL-heavy codebases.

How

1. edgedb project init 2. Define schema in .esdl 3. Create migration 4. Query with EdgeQL 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

const users = await e.select(e.User, () => ({ name: true, posts: { title: true }, })).run(client);

Common Problems

⚠Schema migration conflicts — use edgedb migration create
⚠EdgeQL syntax unfamiliar — review query builder docs
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use computed properties for derived fields
✓Leverage links for relationships instead of joins
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is EdgeDB and what projects is it for?

EdgeDB — next-generation object-relational database on PostgreSQL. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with EdgeDB in 10 minutes?

Two steps: (1) edgedb project init; (2) Define schema in .esdl. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with EdgeDB and how do I avoid it?

The most common pitfall is: Schema migration conflicts — use edgedb migration create. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for EdgeDB?

Best practices for EdgeDB include: Use computed properties for derived fields; Leverage links for relationships instead of joins; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use computed properties for derived fields" — should be set up at project init to avoid costly rework later.

When should I NOT choose EdgeDB?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). EdgeDB shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.