Won't Python be a total bottleneck from compute perspective and concurrency perspective?
Show HN: EdgeDB 1.0
221–230 of 332 posts
Re: Show HN: EdgeDB 1.0
#222Looks great, but the example for SQL looks kind of bad. Is that how pg does things? I thought "modern SQL" used CTEs and other fun features, or this that not a thing for pg as much as say snowflake?
Yea the SQL example looks like the intentionally made it way worse than it needed to be...
It was taken from Elvis' talk. Here's the video explaining how we get to this query and why: https://youtu.be/WRZ3o-NsU_4?t=1892
Re: Show HN: EdgeDB 1.0
#223first commit 2009, so we'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.
It's a long story :-) https://www.edgedb.com/blog/building-a-production-database-i...
I always appreciate the historical journey why someone made X the way it is.
Thank you for sharing.
Re: Show HN: EdgeDB 1.0
#224Earlier quoted context omitted.
GraphQL is great for what it was designed for. It just was never designed to be a querying language with analytical capabilities, like EdgeQL.
Forget analytics, it can't even do pagination. That really limits the benefit of being introspectable.
Yeah, true. FWIW with EdgeQL you can also introspect all aspects of your schema.
Re: Show HN: EdgeDB 1.0
#225Won't Python be a total bottleneck from compute perspective and concurrency perspective?
We know a thing or two about concurrency and Python. Take a look at our blog post [1] touching on what we do and how.
[1] https://www.edgedb.com/blog/building-a-production-database-i...
Re: Show HN: EdgeDB 1.0
#226I'm disappointed on you open sourcing it.
Now I'm not against OSS movement and in fact I'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.
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.
So please stop open sourcing too much, I don't want to see the same ill fate again and again for great products like RethinkDB (and its downfall) that could change the world
Re: Show HN: EdgeDB 1.0
#227Congrats on the milestone! I've been following for a while - awesome to see the progress you've made. Q: What are your plans for sharding / scale-out? 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 / graph-like structures, and we make use of columns or jsonb attributes like `{ table: Table, id: UUID }` which sounds lik…
> Congrats on the milestone!
Thanks!
> Q: What are your plans for sharding / scale-out?
Sharding is planned, though there is no set design yet, this area is in early research phase currently. Thanks for sharing your experience by the way! Learnings from the field definitely help. A traditional read replica scale-out is already supported and we are building integrations with Postgres orchestrators (for failover, replica discovery etc). Oh, and automatically routing read-only queries to read replicas (with some controls for lag) is something that we plan as well.
> Q: Do you have plans to support EdgeQL embedding or SQLite?
Possibly. Depends on the application and performance expectations :-) PostgreSQL is really special in its ability to deal with complex queries. We already have a toy EdgeQL interpreter in the codebase [1], which is mostly used to quickly prototype syntax and validate semantics. It would be great to scale it up to something that can work with persistent stores (even if dumb and slow).
> are you considering porting more logic to Rust?
Yes, that the long term plan.
[1] https://github.com/edgedb/edgedb/blob/master/edb/tools/toy_e...
Re: Show HN: EdgeDB 1.0
#228I’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 po…
I would suggest framing distributed systems analysis in terms of PACELC instead of CAP: https://en.wikipedia.org/wiki/PACELC_theorem
Re: Show HN: EdgeDB 1.0
#229EdgeDB co-founder Yury here. Ask me anything :) Live launch stream: https://www.youtube.com/watch?v=WRZ3o-NsU_4
I have a few questions I can't find after skimming the documentation.. Can someone use Postgres extensions with EdgeDB, like TimescaleDB, PostGIS, Zombodb and Postgres_fdw? How are sum types (called enums in Rust) modelled in EdgeDB? (like Rust's Result). Do I need to define it with inheritance, where each variant inherits from it? What about adding specific syntax for sum types? edit: also, I see there's a WIP custo…
Regarding extensions: we plan to wrap the most popular ones like PostGIS to give them idiomatic EdgeQL flavor. We need to do a bit of work to make that the right way.
Sum types can be modeled with inheritance. You can create an abstract base type and use that as target for the links. You can then derive types from it and write polymorphic EdgeQL queries to select/match data.
Rust client is still work on progress, not really open to tinkering unless you want to experiment.
Re: Show HN: EdgeDB 1.0
#230I'm disappointed on you open sourcing it. Now I'm not against OSS movement and in fact I'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. 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 c…
> Instead, you should just release the core version so others will build an open ecosystem around your mainline product.
To be clear EdgeDB is the core version, albeit a large core. We have many ideas about value-adds. But the goal for open sourcing it is indeed to foster an open ecosystem.