Live data from Hacker News

Show HN: EdgeDB 1.0

edgedb.com

181–190 of 332 posts

Re: Show HN: EdgeDB 1.0

#181

Earlier quoted context omitted.

Right, but conceptually the way you interact with it is the same. I'm not trying to belittle what you've done. I'm in fact very excited about it. And EdgeDB is very needed because it's just an Apple library currently. Conceptually, my impression is that EdgeDb is relational tables (highly-typed) queried, combined, and modeled as nodes in a graph/tree. Is that conceptually correct? I don't, but I would like to if I co…

That's correct! Though that's true for most ORMs as well, and we try not to get lumped into the ORM bucket...too much bad blood. I've dabbled with CoreData myself and it's a phenomenal API. Apple comes up with a lot of great stuff. In fact, given how much server-side Swift there is these days, we'll have to look into building a Swift client library at some point.

I completely understand, but your product and CoreData go so much further than what ORMs can. It's fulfilling the promise of ORMs and relational databases that's only existed in people's minds up until recently.

I hope EdgeDB is immediately recognized for the value it will bring to developer productivity everywhere!

Now we just need an SQLite version of EdgeQL (perhaps EQLite) for local data and it can completely replace SQL in my life.

Re: Show HN: EdgeDB 1.0

#183

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…

Maybe I misunderstand what you are saying but it sounds pretty straight forward in SQL.

Re: Show HN: EdgeDB 1.0

#184
post #174

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? On a tangent note, I find it is honestly annoying to have to maintain a separate account/authorization/vpc connection just because I want to use a database. I would much rather startups…

A lot to unpack here.

1. If other clouds want to offer a hosted EdgeDB offering, they can do so. We'll have a tight integration with the `edgedb` CLI and we're confident we can beat them on the developer experience which is our #1 priority.

2. We'll likely use GitHub for auth though this isn't set in stone yet. We're still planning out the workflows surrounding EdgeDB Cloud.

3. As for the explosion of cloud silos—that's a very real phenomenon with a boring reason: hosting is one of the few ways to make money building OSS software. There are preposterously valuable OSS frameworks + libraries that haven't made anyone a cent. We implemented "one-click" deploy buttons for the major clouds to the extent it was possible to do, but for fully open-source companies like EdgeDB there's aren't many routes to sustainability outside of paid hosting.

Re: Show HN: EdgeDB 1.0

#185
post #111

Earlier quoted context omitted.

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 compos…

Would love to see benchmarks! :)

But just for clarity in the discussion thread here, Hasura also compiles to a single query when only Postgres is being hit and I'd expect performance to be quite similar...

Ofcourse, if the GraphQL query requires federation across multiple Postgres databases or multiple databases or databases + other GraphQL / REST APIs, then Hasura breaks them up into multiple queries with a worst-case performance of a data-loader type set up.

Re: Show HN: EdgeDB 1.0

#186
Thank you for the monumental work you guys put into this! Looks very interesting, and something I would like to try out.

One quick question - I see that you have a Rust client, however it's marked WIP, how usable is it in its current state? Any idea on a timeline of it becoming an official binding?

Re: Show HN: EdgeDB 1.0

#187
post #174

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? On a tangent note, I find it is honestly annoying to have to maintain a separate account/authorization/vpc connection just because I want to use a database. I would much rather startups…

A lot to unpack here. 1. If other clouds want to offer a hosted EdgeDB offering, they can do so. We'll have a tight integration with the `edgedb` CLI and we're confident we can beat them on the developer experience which is our #1 priority. 2. We'll likely use GitHub for auth though this isn't set in stone yet. We're still planning out the workflows surrounding EdgeDB Cloud. 3. As for the explosion of cloud silos—tha…

Fair, thanks for the answers! Honestly hopes it works out for you, but I am very cautious about these things. Elasticsearch, Mongo, Timescale all ended up changing license at some point.

Yeah thats ok for startups I guess.

Yeah sad state of affair really, though fully solvable by tech IMO if we had some protocol for integrating services in clouds. In any case, please don't underestimate the terraform integration. I really could not care less about the one-click deploy. What I care about is maintenance and integration with my existing infrastructure as code.

Re: Show HN: EdgeDB 1.0

#188

I'm so happy for you guys, I'm wishing you great success. Since the first first version of uvloop I've been excited about MagicStack and I couldn't be more excited about EdgeDB since it has the same magical minds behind. Here's what I think makes EdgeDB special: it's a DB that replaces the tediousness of ORMs with a better core that can be cross-language / cross-platform. I've implemented tons of APIs, first REST, th…

> it's a DB that replaces the tediousness of ORMs with a better core that can be cross-language / cross-platform

Does it compare to RethinkDB in this regard? The "fluent" native query language, ReQL, was one of its best parts.

Re: Show HN: EdgeDB 1.0

#189
post #179
post #174

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? On a tangent note, I find it is honestly annoying to have to maintain a separate account/authorization/vpc connection just because I want to use a database. I would much rather startups…

Re license we have an answer for you here: https://github.com/edgedb/edgedb/discussions/3377 Re second point you can deploy edgedb to your cloud of choice. As for working with cloud providers to make integration better for the user, it's a bit too early for us to comment.

Thanks!

Cloud of choice is great, also need region and AZ of choice too for any serious production database. What is killing performance is round trip time to the DB. The language seems to help on the number of round-trips so that's good.

Re: Show HN: EdgeDB 1.0

#190
post #189
post #179

Earlier quoted context omitted.

Re license we have an answer for you here: https://github.com/edgedb/edgedb/discussions/3377 Re second point you can deploy edgedb to your cloud of choice. As for working with cloud providers to make integration better for the user, it's a bit too early for us to comment.

Thanks! Cloud of choice is great, also need region and AZ of choice too for any serious production database. What is killing performance is round trip time to the DB. The language seems to help on the number of round-trips so that's good.

> The language seems to help on the number of round-trips so that's good.

Yep, you got it! :)

Post reply on HN