Crazy Wisdom
Episode #415: Rethinking Databases: EdgeDB’s Blueprint for a Developer-Friendly Future
- EdgeDB
- relational databases
- SQL
- schema
- object-relational impedance mismatch
- PostgreSQL
- database abstraction
- query language
This video isn't available here. Try YouTube, or listen to the audio below.
Watch on YouTubeAbout this episode
Timestamps
Key Insights
- Reimagining Relational Databases: Yury Selivanov explains how EdgeDB represents a modern rethinking of relational databases. Unlike traditional databases designed with 1970s paradigms, EdgeDB focuses on improving developer experience by introducing object-oriented schemas and hierarchical query capabilities, bridging the gap between modern programming needs and legacy systems.
- Bridging Data Models and Code: A key challenge in software development is the object-relational impedance mismatch, where relational database tables do not naturally map to object-based data models in programming languages. EdgeDB addresses this by providing a high-level data model and query language that aligns with how developers think and work, eliminating the need for complex ORMs.
- Advancing Query Language Design: Traditional SQL, while powerful, can be cumbersome for application development. EdgeDB introduces EdgeQL, a modern query language designed for readability, hierarchical data handling, and developer productivity. This new language reduces the friction of working with relational data in real-world software projects.
- AI as a Tool, Not a Replacement: While AI has transformed coding productivity, Yury emphasizes that it is a tool to assist, not replace, developers. LLMs like GPT can generate code, but the resulting systems still require human oversight for debugging, optimization, and long-term maintenance, highlighting the enduring importance of experienced engineers.
- The Role of Schema in Data Integrity: Schema-defined databases like EdgeDB allow developers to codify business logic and enforce data integrity directly within the database. This reduces the need for application-level checks, simplifying the codebase while ensuring robust data consistency—a feature that remains critical even in the era of AI.
- Integrating AI into Databases: EdgeDB is exploring innovative integrations of AI, such as automatic embedding generation and retrieval-augmented generation (RAG) endpoints, to enhance data usability and simplify complex workflows. These capabilities position EdgeDB as a forward-thinking tool in the rapidly evolving landscape of AI-enhanced software.
- Balancing Adoption and Usability: To encourage adoption, EdgeDB is incorporating familiar tools like SQL alongside its advanced features, lowering the learning curve for new users. This approach combines innovation with accessibility, ensuring that developers can transition seamlessly to the platform while benefiting from its modern capabilities.
Episode transcript
Welcome to the Crazy Wisdom Podcast. This podcast is for you. If you have an insane drive to find the truth of things, it's not the good answers that we seek, but the good questions. I interview a range of different guests from many different fields, all with the intention to uncover the simple truths that are hidden in plain sight. Most people don't want to go there. I go there, my guests go there, and you benefit. Please let me know if you enjoy these episodes and as always, subscribe on itunes, Spotify or wherever you listen to the podcasts.
Welcome to the Crazy Wisdom Podcast. Today my guest is Yuri Selivanov and He is the CEO and co founder of EdgedB. And we're going to get into what exactly EdgedB is because I have a AI whisperer down here in Buenos Aires who's a senior developer and he told me that EdgedB might, might actually fit into what I want to build. And so welcome to the show, Yuri.
It's essentially a reinvention of relational database from scratch. Given modern requirements to application development, we actually want to make databases easier to work with. And it's not a big secret in the industry that developers don't really like databases and dealing with them. And one of the reason for reasons for that is that relational databases were invented in the 70s and most of the decisions for the syntax of the query language, for the data model, how you define your databases, it was defined in that period and it was never properly challenged. So while the rest of the ecosystem evolved drastically, we have so many different programming languages that didn't exist in the 70s or even like 20 years since 70s. We haven't seen anything like that happen to the database world and with HDB will want to change that.
Your first full transcript is free. After that, an email opens every transcript in the index — a list of readers we can write to, not a guest book.