Show HN: EdgeDB 1.0

I’ll add to the positivity: this is the first time I’ve ever found a “we can do better than SQL” compelling. It’s easy to understand what it’s doing with a variety of known quantities. It solves a difficult problem elegantly. It has 100% overlap with the goals I want it to have. It’s designed to be usable with minimal fuss. It does really a good job of portraying itself as magic (it will be awesome to use) without portraying itself as magic (it explains itself in terms of already knowable tools and how it leverages their strength).<p>I do have a couple minor quibbles:<p>- Serializable transactions are expensive, and that deserves to be an explicit caveat. Not everyone knows this, and it’s an important thing to put up front.<p>- Some of the language in this post are in CAP theorem territory but neglect to directly address that. I’d like to see how client usage compares with direct Postgres usage (idiomatic for each insofar as such a beast exists) in a Call Me Maybe. I know that’s a lot to ask in a 1.0 announcement four years in the making, but I hope it’s a priority to get this in front of Aphyr.<p>Edit: oh and I definitely look forward to this being further distinguished from an ORM, because even though I can see the blue and black dress my mind keeps switching it back to gold and white.

I&#x27;m so happy for you guys, I&#x27;m wishing you great success. Since the first first version of uvloop I&#x27;ve been excited about MagicStack and I couldn&#x27;t be more excited about EdgeDB since it has the same magical minds behind.<p>Here&#x27;s what I think makes EdgeDB special: it&#x27;s a DB that replaces the tediousness of ORMs with a better core that can be cross-language &#x2F; cross-platform. I&#x27;ve implemented tons of APIs, first REST, then GraphQL all of them on top of ORMs (Django, Peewee, SQLAlchemy, Mongoose and more). When prototyping was great, but scaling them became quite challenging, specially if you want to have a performant outcome when retrieving data.<p>EdgeQL is an incredible useful abstraction that will prove itself in a few years. Long life EdgeQL. Keep up the good work!

These guys are from magic stack, they wrote the definitive async python postgres library, asyncpg. Very high quality library.<p>Been keeping a close eye on Edge, had even considered it as a primary database, and probably will in the future!!<p>As much as I adore the ergonomics improvements I really am more interested in the performance, replication, scalability story, with the likes of cockroach db reaching maturity in 2022.<p>But as a postgres replacement in general, I would highly consider using edge.

I feel like a graph database is a solution to an issue I&#x27;ve faced (and, continue to face) and it may just be because that I haven&#x27;t spun one up and tried or that the documentation&#x2F;examples don&#x27;t stick out. But could someone confirm my feeling? If my feeling is correct, I&#x27;d enjoy verifying it with EdgeDB or the like.<p>My example&#x2F;requirement: I have a user wanting to find best-matching blog posts. Every post is tagged with a given category. There could be 100+ categories in the blog system and a blog post could be tagged with any number of these system categories. A user wants to see all posts tagged with &quot;angular&quot;, &quot;nestjs&quot;, &quot;cypress&quot; and &quot;nx&quot;. The resulting list should return and be sorted by the best matches, to those of least relevance. So, posts that include all four tags should be up top and as the user browses down the results, there are posts with less matching tags.<p>What I&#x27;ve seen with SQL looks expensive, especially if you search with more and more tags. I may just not know what to search for though, re. SQL. Is there a query against a graph database that could accomplish this?

What&#x27;s a good way to develop a mental model about what&#x27;s happening under the hood in EdgeDB?<p>With SQL, I have a mental model of how things work under the hood. For instance, I think of each table as being stored separately on disk, containing &quot;rows&quot;. And the rows are really just equally-sized data blocks that are laid out back to back. B+ trees, with leaf nodes that point to (or just are) the rows, are used for indexes.<p>When I&#x27;m designing SQL schemas, I use this mental model to make guesses about performance. And when my queries are slow, I look at the execution plan.<p>My question is, how can I develop a similar intuition about EdgeDB? Under the hood, how are types and links stored in Postgres? And if I&#x27;m having performance issues, can I see an execution plan?

Could someone explain what a graph-relational database is? I&#x27;m not able to extract a technical definition from the paragraph below:<p>&quot;What is a graph-relational database? EdgeDB is built on an extension of the relational data model that we call the graph-relational model. This model completely eliminates the object-relational impedance mismatch while retaining the solid basis of and performance of the classic relational model. This makes EdgeDB an ideal database for application development.&quot;

The live presentation is happening right now: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WRZ3o-NsU_4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WRZ3o-NsU_4</a><p>Very interested in what data engineers think about this project!<p>I am not a developer, but the founders (including Yury Selivanov, Python Core Developer, see also <a href="https:&#x2F;&#x2F;github.com&#x2F;MagicStack" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;MagicStack</a>) and the fact that these people have been investing in the project for four years already, make me think that EdgeDB can be an important project for the database world!

Sounds pretty cool!<p>Questions:<p>1. What is the story for replication currently? Can I use EdgeDB with Posgres replication tools like Stolon or Patroni, running EdgeDB against the proxy they expose?<p>Or does EdgeDB plan&#x2F;need to have its own replication?<p>Googling this, I found this previous HN post (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=19640689" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=19640689</a>) saying:<p>&gt; Tooling for that will be coming in the next few alpha releases.<p>2. &quot;A builtin migration system that can reason and diff schemas automatically or interactively&quot;<p>How do you deal with the fact that Posgres does not offer transactional DDL (e.g. ALTER TABLE)?<p>In our Posgres, we had to use advisory locks around migrations to avoid concurrent schema changes invoked by concurrently starting servers which run migration.

Won&#x27;t the functional variant read better than the SQL dialect<p><pre><code> movie_reviews .filter(_.actor.name.lowercase() == &quot;Zendaya&quot;) .groupBy(_.title, _.credit_order, avg(_.ratings)) .sortBy(_.credit_order) .take(5) </code></pre> vs.<p><pre><code> select Movie { title, rating := math::mean(.ratings.score) actors: { name } order by @credits_order limit 5, } filter &quot;Zendaya&quot; in .actors.name</code></pre>

This is so exciting. We can definitely do better than SQL in 2022 and EdgeDB is a step in the right direction. Been using Prisma[0] in production in the past year and a half (which takes the same approach as EdgeDB but currently works for TypeScript and Golang) and I&#x27;m so happy. [0]: <a href="https:&#x2F;&#x2F;www.prisma.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.prisma.io&#x2F;</a>

EdgeDB co-founder Yury here. Ask me anything :)<p>Live launch stream: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WRZ3o-NsU_4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=WRZ3o-NsU_4</a>

Hell yeah. This is what I&#x27;ve wanted ever since I first learned about Apple&#x27;s CoreData.<p>This seems great. I have a highly interrelated data model (think parsed natural language text with annotations), and writing SQL to keep all of that data aligned and synced is a pain with an ORM.<p>Am I right in imagining this works similarly to how Apple&#x27;s CoreData does? It lets you build objects linked to each other but handles all of the joining and syncing of the data for you to keep the object model in mind.<p>In the same vein will you be creating a Swift client?

&gt; This is why we wrote (and will continue writing) full-featured first-party database client implementations for common programming languages (currently available for Python, JavaScript&#x2F;TypeScript&#x2F;Deno, and Go).<p>Why no C API? Pretty much every language has a C FFI, PostgreSQL&#x27;s libpq is in C too, and then it&#x27;s easy to make bindings from other languages. But with a few individual implementations in other languages it&#x27;s not as easy to use from more languages. Always makes me to wonder about these decisions when I see projects heading that way.<p>Unrelated to the subject, but the text on the website is #B3B3B3 on #FFF, which is hard to read as is, and violates WCAG recommendations. When overwriting it with a custom CSS, it&#x27;s visible that headings have weird margins, covering parts of text before them.<p>While looking for more, I noticed that the website suggests to `curl | sh` things in the introduction, which is quite awkward too (and a subject of light flamewars), adding another barrier.<p>The brief project description made me to wonder how well it abstracts out PostgreSQL (and how to work with the databases it creates via PostgreSQL itself, if it&#x27;s possible at all, how to debug it when things will go wrong), but after brief skimming there&#x27;s no PostgreSQL bits in sight: just a special shell, a dedicated language, its own drivers. Which is a bit scary.<p>Neither have I found a description of its graph-relational model, how it&#x27;s built on top of PostgreSQL, how one can be sure that it&#x27;ll work more or less smoothly, how things like profiling are done (or is it designed to never need explicit profiling&#x2F;optimization?), is there more to it than PostgREST-like interface abstracting out the SQL bits for DDL too.<p>Looks like an interesting project overall though.

&gt; We should not continue wasting our productivity with a database API architecture from the last century.<p>Sorry, but dissing proven technology like this just makes me vomit. Show me _how_ you can beat SQL in performance and features on the frontpage, or I&#x27;m just happy to go along with what I already have.

This seems kind of cool, but honestly the benefits described don&#x27;t really solve actual problems I&#x27;ve run into in development. The overall article reads like marketing talk and doesn&#x27;t actually describe concretely why it&#x27;s better than existing solutions. For something as core as a database I would expect more rigorous descriptions and benchmarks.<p>&gt; We shall do better than SQL The EdgeQL language looks cool, and I&#x27;m sure querying via a graph structure makes certain problems easier in some use cases. However as much as people have complained about SQL, it&#x27;s just so ubiquitous there needs to be a very good reason to switch away from it. Not having to write joins isn&#x27;t really a good enough reason, in my opinion.<p>&gt; The true source of truth I&#x27;m not sure why this means EdgeDB is better. Tons of applications use a traditional or cloud SQL database as the source of truth right now. This section seems to imply with microservices you no longer have a single source of truth. But if they&#x27;re trying to say a microservice system should instead us a single common database that breaks separation of concerns and moves us into an annoying situation where you have a bunch of services communicating via a shared database.<p>&gt; Not just a database server It sounds like they have a solid client, which is awesome.<p>&gt; Cloud-ready database APIs &gt; The vast scale of modern application deployments requires that inelastic computing resources are managed very carefully. Until cloud-native databases reach complete functional and performance parity with traditional databases, we will have to contend with the fact that the database is a scarce resource.<p>This used to be true, but is definitely no longer true. Cloud-native databases are everywhere and incredibly common. See any major cloud, <a href="https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;</a>, or any of the tons of other database solutions.<p>It&#x27;s great to see a new database coming out - innovation in the space is super important. However this announcement reads like marketing speak, and is light on the details. When I see a new product I want to hear things like: - about how it scales - what the architecture is - why is it stable and trust-worth enough to put my data on - is it multi-node? How did they make it serializable? - how fast is it? Performance is super important.<p>Based on their website it seems like a thin skin over postgresql. If that&#x27;s the case I&#x27;ll just use postgresql. If it&#x27;s a clustered new and advanced database, then I&#x27;ll be wary about trusting it for anything real.

EdgeQL looks really nice. I do think this will be somewhat hard to sell because at small scales SQL and basic ORMs mostly work and have less lock-in. At large scales folks also want a lot more operational features like scaling out, control of the underlying schema for performance reasons, relaxing some constraints for horizontal sharding, and so on.<p>I think EdgeQL (and the data model) has potential for being a lot more than accessing the database. For example, you could have a distributed system use this data model across various typically replicated data stores - include all caches and &quot;materialized views&quot; of various kinds. Extend EdgeQL to define various caches and computed values from the core schema. Then you could use it to represent querying the same data but with different freshness. Now this becomes a compelling idea. Essentially it gives you a well defined way to declare and manage various computed values, laggy caches without having to manually implement all that coordination.

Can someone from EdgeDB explain why the SQL isn&#x27;t as simple as what I have below? What am I missing? Why is that cross join lateral necessary:<p><pre><code> SELECT title, ARRAY_SLICE(ARRAY_AGG(movie_actors.name WITHIN GROUP (order by movie_actors.credits_order asc)),0,5) avg(movie_reviews.score) FROM movie JOIN movie_actors on (movie.id = movie_actors.movie_id) JOIN person on (movie_Actors.person_id = person.id) JOIN movie_reviews on (movie.id = movie_reviews.id) WHERE person.name like &#x27;%Zendaya%&#x27; group by title</code></pre>

EdgeDB employee here. We&#x27;re beyond excited to finally publish a stable release of EdgeDB after 4 years of active development and 15 pre-releases. Happy to answer any questions on here!

Why is it called Edge though?<p>I immediately assumed it was some kind of distributed db running at the edge but it seems this is not the case.

It&#x27;s a good sales pitch, but it&#x27;s not immediately clear what the terms are. I see that there is a company behind this, that there&#x27;s also a Github repo, and it appears you can install something without paying. But is it entirely open source? If not, what are they selling? What kind of business is this?

Where does full text search fall into the picture &#x2F; current query language? Do I need to drop down to writing SQL for that?<p>When do you drop down to SQL &#x2F; where does the boundary end for edgeQL?

Hmm, no JVM or .NET support ... seems problematic for any widescale adoption at this point. Are there fundamental reasons why this is problematic or just not got around to it?<p>(And, is it likely to be possible to build it against standard interfaces like JDBC - or is it too different?)

On <a href="https:&#x2F;&#x2F;www.edgedb.com&#x2F;tutorial&#x2F;basic-queries&#x2F;objects" rel="nofollow">https:&#x2F;&#x2F;www.edgedb.com&#x2F;tutorial&#x2F;basic-queries&#x2F;objects</a>, if I change &quot;SELECT User.name;&quot; to &quot;SELECT User.Name;&quot; the page crashes with, &quot;Application error: a client-side exception has occurred.&quot; It crashes on Chrome and Edge.

Congrats with 1.0. A couple of things I’m curious about:<p>1. How does EdgeDB compare to Supabase? Thinking both of realtime functionality and row-level security. 2. If I was to use EdgeDB instead of Django, how would I go about it? In other words, how can I set up a batteries-included, server-side web app?

I can’t find anything in the docs on security. PostgreSQL has a pretty solid authorization story with row level security etc. Does EdgeDB provide any similar authorization mechanisms to ensure only data the user is entitled to is returned in queries?

Congrats on the launch! The code seems to be Apache 2.0 which opens the door to AWS or other big clouds just hosting the service instead of people using your cloud service. Are you guys planning to change the license to prevent that?<p>On a tangent note, I find it is honestly annoying to have to maintain a separate account&#x2F;authorization&#x2F;vpc connection just because I want to use a database. I would much rather startups work with cloud providers to offer it natively or we invent a better way to interoperate with clouds. The explosion of small &quot;cloud&quot; that offer one service each isn&#x27;t pleasant to work it especially when they don&#x27;t have a terraform provider.

first commit 2009, so we&#x27;re roughly 12 years later. Whats the saying? It takes about 10 years to create a reliable DB? Good on you guys. Looks super interesting.

This looks phenomenal guys. I&#x27;ve read a bunch of these Show HN posts over the years and I struggle to stay engaged on most of them. They always lean towards highly technical that makes my small brain smooth over or so much marketing speak that I have no idea what&#x27;s going on. Your post was short enough to comprehend in one sitting, you have an example near the beginning and you make your case clearly. I love that you used Postgres as a layer and I think that set you up for success. You have me excited and I&#x27;m pretty pumped to use edgedb in one of my idea projects just to get a feel for how it works.<p>Congrats!

Does it include (or have planned) any features relating to full text search, more specifically for mixing ranking&#x2F;search with graph queries?<p>One use case I have (solved by some current graph DBs) is performing a complex full text search (boolean operators, stopword removal, fuzzy matching etc.), which alters search ranking based on graph properties (e.g. a node with more edges might get a reduction in score, the root of a tree might get a boost, etc.).<p>I&#x27;m still going through the tutorial, so haven&#x27;t got to grips with what the DB is capable of yet.

One thing that can facilitate adoption is a smooth path from a working software based on Postgresql to EdgeDB:<p>We have a software that&#x27;s a GraphQL interface to a database that&#x27;s populated with a project (let&#x27;s call it the indexer project) we do not control. It would be great if we could check the database schema for problems it might have to be used as an EdgeDB database. Then we would migrate our application to use EdgeDB, while the indexer keeps loading our database through direct interaction with PostgreSql.

This query language looks really nice!<p>I wish GraphQL were more like this and considered built-in features like where clauses and cursors, instead of having to add those over the top with loose conventions.

<i>EdgeDB is built on an extension of the relational data model that we call the graph-relational model. This model completely eliminates the object-relational impedance mismatch while retaining the solid basis of and performance of the classic relational model.</i><p>I don&#x27;t see how can they retain the performance of the relational model when using graphs on top of PG unless they are using PG as storage k&#x2F;v layer only.

Poking a bit at the documentation, I see like&#x2F;ilike but are there plans for text search&#x2F;trigram capabilities? Recently I’ve been working with lots of different entities that have searchable properties and exploring searching across different elasticsearch indexes to do “JOIN” like operations but have been exploring Postgres (and related) solutions for better “JOIN” support out of the box

I don&#x27;t understand the benefit. It&#x27;s just a query language on top of Postgres? It doesn&#x27;t seem to have the performance characteristics of a graph database, while acting like it does. JOINS will still be expensive. You guys shouldn&#x27;t use the word graph, misleading.

Why a new language? I can see and understand why and where graphs beat out SQL, but what does EdgeQL have over existing graph languages?<p>Eg. vs Cypher or the likely-Cypher-compatible forthcoming GQL standard? <a href="https:&#x2F;&#x2F;www.gqlstandards.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.gqlstandards.org&#x2F;</a>

Thank you for the monumental work you guys put into this! Looks very interesting, and something I would like to try out.<p>One quick question - I see that you have a Rust client, however it&#x27;s marked WIP, how usable is it in its current state? Any idea on a timeline of it becoming an official binding?

I wonder how EdgeDB talks to postgres. Does it speak the Postgres protocol and translate the queries, or is it more of a deeper integration in to the storage layer?<p>Very interested in this! I&#x27;ve been wanting to build a generic HATEOAS server and this feels like this might be the right database!

I know benchmarking DB is very hard and pretty much nonsense, but do you have any idea &#x2F; production use cases of EdgeDB at large scale? Did you see a performance drawback given from the higher abstraction, and the EdgeDB stateless client between the app and postgre?

At the time of writing, docs have a large typo in them: <a href="https:&#x2F;&#x2F;www.edgedb.com&#x2F;docs&#x2F;clients&#x2F;01_js&#x2F;driver" rel="nofollow">https:&#x2F;&#x2F;www.edgedb.com&#x2F;docs&#x2F;clients&#x2F;01_js&#x2F;driver</a><p>impoart * as edgedb from &quot;edgedb&quot;;

EdgeQL seems like a custom graphQL. Any reasons you did not follow dgraph&#x27;s DQL or graphQL-compatible language? <a href="https:&#x2F;&#x2F;dgraph.io&#x2F;docs&#x2F;get-started&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dgraph.io&#x2F;docs&#x2F;get-started&#x2F;</a>

If anyone makes this work with heroku Postgres, let me know!<p>I started a container and connected it, but instantly got an email from heroku telling me i had 19500 of my 10000 rows, and 215 tables. Not really any hobby-project viable priced hosting options in their documentation.

This looks pretty cool. I&#x27;d be interested to hear when the Rust bindings will be production ready: <a href="https:&#x2F;&#x2F;github.com&#x2F;edgedb&#x2F;edgedb-rust" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;edgedb&#x2F;edgedb-rust</a>

I&#x27;m disappointed on you open sourcing it.<p>Now I&#x27;m not against OSS movement and in fact I&#x27;m working at a company doing exactly this, but releasing your bread-and-butter as an open source project leaves you vulnerable to peer plagiarism.<p>Instead, you should just release the core version so others will build an open ecosystem around your mainline product. This will secure your market fundamentals by making sure no one could overshadow you especially in a fiercely competitve market of database.<p>So please stop open sourcing too much, I don&#x27;t want to see the same ill fate again and again for great products like RethinkDB (and its downfall) that could change the world

Hi, looks really great! Thanks for this great piece of tech!<p>I have a question regarding the migrations, in the website you say it&#x27;s safe to run them with automated flow, we know it uses Postgres under the hood and we know that sometimes migrations on large datasets can cause downtime in the database clusters. How do you handle them? I guess since you don&#x27;t have a backing &quot;users&quot; table for a &quot;User&quot; model adding &#x2F; removing fields is not actually happening the same way it happens in a normal relational database, thus it&#x27;s not a blocking or resource consuming operation for you?

How does this compare against neo4j? When should I choose one instead of the other?

Looks great, but the example for SQL looks kind of bad. Is that how pg does things? I thought &quot;modern SQL&quot; used CTEs and other fun features, or this that not a thing for pg as much as say snowflake?

&gt; EdgeDB is built on top of Postgres<p>How it is a new database? Or an advanced orm?

What&#x27;s the sort of timeline on GIS extensions? Great work btw, I&#x27;ve been following since the alphas and I&#x27;m excited to try it out :)

I&#x27;m skeptical of any fancy new database, because they have always been disappointing in one way or another, but this looks really promising!<p>ORMs work fine for relational data, until there&#x27;s a lot of edge data on the joins. I looked at the docs on mobile and couldn&#x27;t find an answer, how does EdgeDB handle data on joins? E.g. GraphQL &quot;connection&quot; types with edges.

I only glanced through this, but would you say there’s some vague similarities (ignoring the distributed&#x2F;caching aspects) to Facebook’s TAO here? For example, as a user of this, would I have to care about the Postgres schema, or is that abstracted away from me?<p>(Tao uses mysql and stores graph data as pretty much key&#x2F;value pairs, and then a layer on top to query it)

I love the feature set. Great work! Hard to believe this is the first major release. Are you guys planning to add C# client support?

Congrats on the milestone! I&#x27;ve been following for a while - awesome to see the progress you&#x27;ve made.<p>Q: What are your plans for sharding &#x2F; scale-out?<p>At Notion, we run ~480 logical schemas spread across ~32 Postgres databases [1]. Our data model [2] (sorry for the blog post spam) has a recursive &#x2F; graph-like structures, and we make use of columns or jsonb attributes like `{ table: Table, id: UUID }` which sounds like your polymorphic links feature. It seems like EdgeDB&#x27;s model lines up well with how we already use our database.<p>I did a quick cmd-f here, on the linked announcement, and in your docs looking for &quot;shard&quot; and &quot;scale&quot; but didn&#x27;t find any relevant results. Postgres needs a Vitess!<p>Q: Do you have plans to support EdgeQL embedding or SQLite?<p>I am always looking for a way to compile &quot;better than SQL&quot; languages down to SQL. I like Datalog in this area because it&#x27;s a composable way to define relationships&#x2F;facts&#x2F;derivations but no one is putting serious business effort to this idea (honorable mention to logica [3]). EdgeQL also fits the bill -- queries aren&#x27;t logical, but they are composable -- plus looks easier to teach than most Datalog variants.<p>I took a peek in the repo and saw that a few EdgeQL components are written in Rust [4]; are you considering porting more logic to Rust? That would make EdgeQL much more embeddable - it could run in WASM or linked into an Android&#x2F;iOS app. My pie in the sky dream is to use a single composable query&#x2F;logic language to define all my relations and queries, and then compile that stuff so it works the same on both the client, server DB, and data streams (for incremental materialized views, ideally on both client &amp; server).<p>If EdgeDB had a Lite version that ran on SQLite, we&#x27;d be 66% of the way there.<p>(To get the materialized view bits <i>on the server</i>, a mad scientist might already be able to point EdgeDB at Materialize [5])<p>[1]: <a href="https:&#x2F;&#x2F;www.notion.so&#x2F;blog&#x2F;sharding-postgres-at-notion" rel="nofollow">https:&#x2F;&#x2F;www.notion.so&#x2F;blog&#x2F;sharding-postgres-at-notion</a><p>[2]: <a href="https:&#x2F;&#x2F;www.notion.so&#x2F;blog&#x2F;data-model-behind-notion" rel="nofollow">https:&#x2F;&#x2F;www.notion.so&#x2F;blog&#x2F;data-model-behind-notion</a><p>[3]: <a href="https:&#x2F;&#x2F;opensource.googleblog.com&#x2F;2021&#x2F;04&#x2F;logica-organizing-your-data-queries.html" rel="nofollow">https:&#x2F;&#x2F;opensource.googleblog.com&#x2F;2021&#x2F;04&#x2F;logica-organizing-...</a><p>[4]: eg <a href="https:&#x2F;&#x2F;github.com&#x2F;edgedb&#x2F;edgedb&#x2F;tree&#x2F;master&#x2F;edb&#x2F;edgeql-parser&#x2F;src" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;edgedb&#x2F;edgedb&#x2F;tree&#x2F;master&#x2F;edb&#x2F;edgeql-pars...</a><p>[5]: <a href="https:&#x2F;&#x2F;materialize.com&#x2F;docs&#x2F;overview&#x2F;architecture&#x2F;" rel="nofollow">https:&#x2F;&#x2F;materialize.com&#x2F;docs&#x2F;overview&#x2F;architecture&#x2F;</a>

Hi. Is there architecture document explaining all moving parts ? And tracing what is happening from beginning of query to result?

Any timelines on when i can use this with rust? I love this syntax.<p>Edit: Wow, after starting to read the book you guys have done a fantastic job of making it a joy to learn. Learning a database technology by following dracula? amazing.<p>PLEASE PLEASE PLEASE giving this first class support in rust. The select statments reminds me of structs and you even have enums.

For this query to work which is shorter than SQL<p>select Movie { title, rating := math::mean(.ratings.score) actors: { name } order by @credits_order limit 5, } filter &quot;Zendaya&quot; in .actors.name<p>Do I need to write some metadata layer so this higher level query would know what&#x27;s going on? Similar to LookerMl?

Congrats on the launch. I watched the live stream yesterday.<p>I&#x27;m particularly excited about the HTTP and the GraphQL interface. This could potentially mean no need for a backend. One thing I am curious about it the authorization part of it - how can I limit the result set, similar to Row Level Security in Postgres?

I love the look of this, but I&#x27;ve been burned by going all in on exciting projects before (rethink, merb,...) It might be a good idea to add some more info on the team behind, if they have funding to continue etc. MagicStack and uvloop are really worth connecting the dots with.

&gt; Powered by PostgreSQL.<p>You might need to worry about this in two senses:<p>1. Graph constructs aren&#x27;t first-class citizens in the backend. Various potential performance improvements will necessarily be missed.<p>2. PostgreSQL is ok&#x2F;good for transactional work, not good for analytical work, like columnar DBMSes.

I tried the beta around August last year. I struggled grokking it mostly because I had had very minimal experience with SQL - which it kind of assumed you already know the drawbacks of. However, I did like the idea very much.<p>Looking forward to giving it another try soon!

Won&#x27;t Python be a total bottleneck from compute perspective and concurrency perspective?

I didn&#x27;t have a very in-depth look, but it looks like you try to solve a lot at once. So I could replace graphQL and permissions with just edgeDB? Sounds nice, but I&#x27;m sceptical.<p>And edit: why is there no Java&#x2F;Kotlin client?

Nice. This seems so pragmatic - making something to make developers lives easier rather than doing something clever. I could see myself using this in personal projects. (My day job is heavily MS so wont be using it there)

Arggh why is &quot;order by&quot; two space-separated words in their language?<p>If we&#x27;re going to replace SQL the silly 1960s pseudo-English syntax is one of the things we want to get rid of, not retain.

This looks really cool!<p>Are you going to support some kind of subscriptions for realtime?

It looks cool but am I mistaken that this is map reduce just consolidated into a query format? Very very cool for fun projects. As for work projects I&#x27;ll wait for the Jepsen post.

Can you front cockroachdb as it exposes a (mostly) postgresql api?

I think this work is absolutely commendable, but at the end of the day it&#x27;s a database written in Python with Rust extensions sprinkled here and there. Is 1.0 your MVP?

Typo in the post &quot;and also retrive the list of top 5&quot;<p>should be retrieve

How do you want to make money? Do you want to implement autoscale solution or how ?, this sounds increadibly in quite stagnate environment, good look I will give it a try

Congrats - this looks really interesting, and this is coming from a person who generally ignores new shiny database news. Def will be checking this out!

This looks like a better prisma. Too bad its using postgresql. It will not scale. Do you plan to develop your own backend or support others one ?

Very exciting product, congratulations on the launch!

Orientdb is also sql like syntax graph database with way more traction. So this is not the first attempt at this type of databases.

Congrats! Can I get the ebook as pdf somewhere?

The query language reminds me a lot of JPA, which makes sense because this is essentially an ORM layer on top of Postgres.

&gt; the first open source, graph-relational database<p>OrientDB?

I&#x27;ve worked with ArangoDB recently and very much liked their AQL. How Edge compares with Arango?

FYI: your homepage makes my fan start up. Macbook Air, 2020. Chrome reports 30% on GPU process.

Is this a potential alternative to graph databases too? How does it compare to them?

Hurray!

How well does it scale? Any benchmarks and performance metrics?

Looks great. Will try this out!<p>Would a graphql API be part of your roadmap?

Great project. Can this be used from rust somehow?

Looks very good. Who uses it in production?

When intellij datagrip supports it I&#x27;ll try it

how well does it scale?