EdgeDB is a next-generation graph-relational database designed as a spiritual successor to the relational database.
It inherits the strengths of SQL databases: type safety, performance, reliability, and transactionality. But instead of modeling data in a relational (tabular) way, EdgeDB represents data with object types containing properties and links to other objects. It leverages this object-oriented model to provide a superpowered query language that solves some of SQL’s biggest usability problems.
EdgeDB is a complex system, but we’ve structured the documentation so you can learn it in “phases”. You only need to learn as much as you need to start building your application.
Quickstart — Go through the quickstart. It walks through EdgeDB’s core workflows: how to install EdgeDB, create an instance, write a simple schema, execute a migration, and write some simple queries.
Showcases — For a speedrun of EdgeDB’s features and syntax, refer to the Showcase pages for Data Modeling and EdgeQL. These pages each contain a set of annotated examples for all major features; it’s a fast, practical way to hit the ground running with EdgeDB.
Documentation — For a more in-depth understanding of EdgeDB’s type system, concepts, and advanced features, go through the Schema and EdgeQL docs in order. The pages are carefully structured to teach EdgeDB in a linear way.
Reference — As you move forward, more advanced or obscure questions are likely answered in the encylopedic Standard Library and Reference sections. The Standard Library section documents all types, functions, and operators. The Reference section contains formal SDL and EdgeQL syntax breakdowns and reference information on our dump format, binary protocol, configuration settings, and more.
To actually build apps with EdgeDB, you’ll need to know more than SDL and EdgeQL.
Deployment — To publish an EdgeDB-backed application, you’ll need to deploy EdgeDB. Refer to Guides > Deployment for step-by-step deployment guides for all major cloud hosting platforms, as well as instructions for self-hosting with Docker.
strict, strongly typed schema;
powerful and clean query language;
ability to easily work with complex hierarchical data;
built-in support for schema migrations.
EdgeDB is not a graph database: the data is stored and queried using relational database techniques. Unlike most graph databases, EdgeDB maintains a strict schema.
EdgeDB is not a document database, but inserting and querying hierarchical document-like data is trivial.
EdgeDB is not a traditional object database, despite the classification, it is not an implementation of OOP persistence.