Easy EdgeDB

Welcome to Easy EdgeDB! It's an interactive, illustrated textbook designed as a one-stop shop for learning EdgeDB.

We started writing this book shortly after the first alpha release of EdgeDB in Spring 2019. For the first time we had a functional version of the thing we'd been thinking about for so long: an open-source database powered by PostgreSQL that combined the strictness of relational databases, the declarative schema of ORMs, and the painless deep querying of GraphQL, without sacrificing power, consistency, or performance.

While plenty of learning material can be found in the documentation, interactive tutorial, and blog posts, we wanted to put together a more immersive experience - a full book. The result is Easy EdgeDB: a book that's sufficiently comprehensive (and fun!) to shepherd an interested beginner through the full set of basic and intermediate EdgeDB concepts.

Easy EdgeDB is a bit of a unique book. Here's how it differs from what you might expect from a typical e-book:

A story to follow

The book is divided into 20 chapters in which we imagine that we are creating a database for a game. The setting for our imaginary game is the scenes and locations from the book Dracula by Bram Stoker, published in 1897. Our job is to think a little about how to represent items like characters, events, locations, and dates in the book in a database used by a role-playing game built separately. In other words, something like Python/JavaScript/Go on the frontend, and EdgeDB as the game's database.

Bram Stoker's Dracula was the perfect choice for this textbook for a few reasons:

• It's a fun read. We're excited to see you give EdgeDB a try and hope to make the introduction as painless and immersive as possible. We think that anyone who has spent an hour or so with EdgeDB will walk away excited about its possibilities, but for that to happen it's our job to make the experience a pleasant one. Bram Stoker's novel has really helped out here.
• It's a so-called epistolary novel: a novel written through the letters, diaries, and communications written by the main characters. That means that each entry has a date and an author, which makes it a great fit for a database.
• It's copyright free. Our book only scratches the surface of what a real database for a game based on this book would be like, but who knows? Maybe some readers will like it enough to take the concept a bit farther and make it into the real thing. And if that's the case, then an open source database based on a book completely free of copyright is the best way to start.

Plain English

We want to give as many people as possible the opportunity to sit down and give EdgeDB a try, and so we've opted for a style of writing that's simple and straightforward. Not baby talk, just plain English. We have three types of people in mind here:

• People unfamiliar with how to build a database but ready to understand how they work if the concepts are explained in a straightforward way,
• People who are familiar with databases but maybe aren't in the mood to wade through dense verbiage for a product they've never seen before,
• People with English as a second (or third, fourth...) language who would much prefer reading a book in plain English for the same reason.

Interactivity and experimentation

Because the book uses the events in the book for the background, we need a database to tie everything together. It will need to show the connections between the characters, locations, dates, and more. It starts with a simple schema (structure) and builds up from there, changing it as we go. The idea is to simulate the mental process for someone new to EdgeDB that has been given the task of putting this all together. That includes sometimes modifying the schema, creating new types, deleting ones that aren't used, and all the tinkering you'd see in real life.

Going through the book, we will learn how to use queries that are more and more complex. Each chapter contains the schema and inserted data that we've built up so far, and a REPL for you to experiment with. On top of that, each chapter has a number of questions for you to solve if you feel like a small challenge.

Beauty

We looked far and wide, and didn't see any rule that a text on database software has to be dry and image free. To give a feel for the beauty of the original work (with a steampunk-ish vibe added for good measure) we teamed up with Damian Dideńko (didiusz on Instagram), an illustrator from Katowice, Poland, to put together some beautiful sketches that combine the atmosphere of the book Dracula with the most important schema and query concepts per chapter.

So let's get started - on to Chapter 1! Or see the full chapter list below:

Full chapter list

• Chapter 1 - Jonathan Harker travels to Transylvania
• Chapter 2 - At the Hotel in Bistritz
• Chapter 3 - Jonathan goes to Castle Dracula
• Chapter 4 - "What a strange man this Count Dracula is."
• Chapter 5 - Jonathan tries to leave the castle
• Chapter 6 - Still no escape
• Chapter 7 - Jonathan finally "leaves" the castle
• Chapter 8 - Dracula takes the boat to England
• Chapter 9 - Strange events in England
• Chapter 10 - Terrible events in Whitby
• Chapter 11 - What's wrong with Lucy?
• Chapter 12 - From bad to worse
• Chapter 13 - Farewell, Lucy. Meet the new Lucy
• Chapter 14 - Jonathan Harker returns
• Chapter 15 - Time to start vampire hunting
• Chapter 16 - Is Renfield telling the truth?
• Chapter 17 - Poor Renfield. Poor Mina.
• Chapter 18 - Using Dracula's own weapon against him
• Chapter 19 - Dracula escapes
• Chapter 20 - The final battle