Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: EdgeDB 1.0

edgedb.com

Post reply on HN
Print view View original

161–170 of 332 posts

Re: Show HN: EdgeDB 1.0

#162

Post by colinmcd »

TheSpiciestDev wrote: post #125

I feel like a graph database is a solution to an issue I've faced (and, continue to face) and it may just be because that I haven't spun one up and tried or that the documentation/examples don't stick out. But could someone confirm my feeling? If my feeling is correct, I'd enjoy verifying it with EdgeDB or the like. My example/requirement: I have a user wanting to find best-matching blog posts. Every post is tagged w…

EdgeDB employee here. I couldn't have asked for a better question to demonstrate the power of subqueries! Here's how I'd do this in EdgeQL:

  with tag_names := {"angular", "nestjs", "cypress", "nx"},
  select BlogPost {
    title,
    tag_names := .tags.name,
    match_count := count((select .tags filter .name in tag_names))
  }
  order by .match_count desc;
Which would give you a result like this:

  [
    {
      title: 'All the frameworks!',
      tag_names: ['angular', 'nestjs', 'cypress', 'nx'],
      match_count: 4,
    },
    {
      title: 'Nest + Cypress',
      tag_names: ['nestjs', 'cypress'],
      match_count: 2,
    },
    {
      title: 'NX is cool',
      tag_names: ['nx'],
      match_count: 1,
    },
  ];

Re: Show HN: EdgeDB 1.0

#163

Post by RedCrowbar »

kall wrote: post #111
1st1 wrote: post #78

Earlier quoted context omitted.

Yeah, we also blogged about this extensively. Here are are some links: Pointed critique at SQL: [1] Benchmarks: [2] and [3] We'll be adding a dedicated benchmarks page to our website soon. [1] https://www.edgedb.com/blog/we-can-do-better-than-sql [2] https://www.edgedb.com/blog/edgedb-1-0-alpha-1 [3] https://www.edgedb.com/blog/edgedb-1-0-alpha-2

In [3] it says "we are assessing the code complexity and performance of a simple IMDb-like website built with Loopback, TypeORM, Sequelize, Prisma, Hasura, Postgraphile, raw SQL, and EdgeDB" but then it goes on to only explain the results of the classic ORMs but not hasura, postgraphile and prisma. Are the full results available somewhere? That classic ORMs are kinda slow is probably not a surprise to anyone, the oth…

We'll post some benchmarks against Hasura et al soon.

"Faster than SQL" is, of course, relative and depends on "what SQL"? EdgeQL compiles into a single query that uses PostgreSQL-specific features. This is a guarantee. No matter how large or complex your query is, if it compiles, it compiles into a single SQL query. Manually written or ORM-generated SQL tends to be "multi-query" due to the whole "standard SQL composes badly" story. And this matters, because if the roundtrip network latency between the client and the server is 10ms, EdgeQL will get you a response in ~10ms, whereas a multi-query approach will in (~10ms X ) even if every individual query is super-quick to compute.

Re: Show HN: EdgeDB 1.0

#164

Post by mstade »

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?

Re: Show HN: EdgeDB 1.0

#165

Post by RedCrowbar »

hackandtrip wrote: post #115

I know benchmarking DB is very hard and pretty much nonsense, but do you have any idea / 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?

We've got some benchmarks in an earlier blog post [1].

EdgeDB is designed to do its job validating and compiling your schema and queries and then get out of the way. In other words, once a query was first parsed and compiled, the cost of the next trip via EdgeDB would be similar to that of pgbouncer, i.e. we'll simply send the compiled SQL to Postgres and proxy the results back to the client. This is why our data protocol uses Postgres framing and encoding.

[1] https://www.edgedb.com/blog/edgedb-1-0-alpha-1

Re: Show HN: EdgeDB 1.0

#166

Post by samhw »

samhw wrote: post #44
RedCrowbar wrote: post #39

Earlier quoted context omitted.

It's built on Postgres, but it isn't a _thin_ wrapper. We lean hard into Postgres query machinery and type system in order to pull off EdgeQL and graph-relational efficiently.

Ah, OK, interesting! I don't have an immediate use case personally, but I wish you guys the very best. Honestly, database space needs way more competition than it has at present. There are countless permutations of the choices that database designers face, so it's a shame there aren't mature products for more of them. I hope this particular permutation turns out to be a good one for lots of people :)

argh - the database space*

Re: Show HN: EdgeDB 1.0

#167

Post by RedCrowbar »

mstade wrote: post #164

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?

Security policy will be part of the next release. See draft RFC [1], although note it's likely not going to be the final syntax.

[1] https://github.com/edgedb/rfcs/blob/865bc48f4050ced99447bd77...

Re: Show HN: EdgeDB 1.0

#169

Post by henryfjordan »

tluyben2 wrote: post #41
1st1 wrote: post #36

Earlier quoted context omitted.

An ebook with Easy EdgeDB ( https://www.edgedb.com/easy-edgedb )?

Yes, maybe I am blind (I am on mobile at the moment), but I would like the PDF of the book if you have it.

It's available as a set of Markdown files in a git repo, if that helps: https://github.com/edgedb/easy-edgedb
Post reply on HN