EdgeDB
Data
object-relational database
SHOW HN2019
How HN took it
9 positive, 31 neutral or asking, 6 mixed, 8 critical, out of 54 comments about the project. Thread score 0.00.
Idea: 3 for, 3 againstDesign: 1 for, 2 againstExecution: 2 for, 0 againstPerformance: 0 for, 1 againstPricing: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Built on PostgreSQL gives data safety and a proven base
From 2 comments
I'm a pretty experienced Data Engineer working at one of the bigger data companies around. I read your copy and landing page, here's what I took away: 1) New database product…
edmundsauto on HNVery well said. I don't want to touch a database product until it has a proven production use for several years. Creating a database is hard, very hard, as history has shown us…
ThinkBeat on HN
EdgeQL and type system redesign is appealing
From 2 comments
I really like the re-imagination of the type system, data model, and the user interface. This is an area where databases could be significantly better than they currently are. My…
jandrewrogers on HNSo this is basically a fork of Postgresql? Interesting. Why not just have an extension? I do like the idea of object oriented queries (without having to go through ORM), and…
nicodjimenez on HN
Good GraphQL integration
From 1 comment
I'm a pretty experienced Data Engineer working at one of the bigger data companies around. I read your copy and landing page, here's what I took away: 1) New database product…
edmundsauto on HN
Objections
Too new and alpha to trust in production
From 3 comments
I'm a pretty experienced Data Engineer working at one of the bigger data companies around. I read your copy and landing page, here's what I took away: 1) New database product…
edmundsauto on HNVery well said. I don't want to touch a database product until it has a proven production use for several years. Creating a database is hard, very hard, as history has shown us…
ThinkBeat on HNCongrats on your launch. While I like the idea, I believe that it would take at least a couple of years to convince people trying out in a real production environment. This is…
buremba on HN
Unclear scalability beyond small datasets
From 1 comment
I really like the re-imagination of the type system, data model, and the user interface. This is an area where databases could be significantly better than they currently are. My…
jandrewrogers on HN
No NULL handling is a questionable design choice
From 2 comments
Why would you replace nulls with empty sets? Now you can't tell if it's empty or just not set. Now I have to track another thing just to tell me if I have touched a thing. Please…
lugg on HN> EdgeQL has no NULL. So how is a missing value in a column represented? A column value is a scalar value, not a "set". As much as I accept that NULL values are a pain to deal…
hans_castorp on HN
Lacks non-Python client libraries
From 1 comment
Not sure if this is correct, but seems like only client APIs are Python or hitting the GraphQL API for anything else. Obviously it's an alpha so not sure what baseline one should…
zmmmmm on HN
Requests
Full-text search support
From 1 comment
Is there any plans to support full-text search?
fuddle on HN
GIS support
From 1 comment
Are there any plans regarding GIS?
azimuth11 on HN
Extension form instead of a Postgres fork
From 2 comments
So this is basically a fork of Postgresql? Interesting. Why not just have an extension? I do like the idea of object oriented queries (without having to go through ORM), and…
nicodjimenez on HNWhat are the chances that in the future, EdgeDB can upstream their changes to Postgre so that EdgeQL could be run on top Postgre as an Extension rather than current way of…
ksec on HN
Questions
Minimal system requirements and replication plans
From 1 comment
I got lots of question, got bit excited while glancing thru docs. What is the minimal system requirements? And what about partitioning, replication, event log, etc. Is there a…
gcoda on HN
How it compares to Hasura and PostGraphile
From 2 comments
Which benefits does EdgeDB have over Hasura which isn't built on top of PostgreSQL but as a layer that runs on top of it and exposes a GraphQL API along with access control,…
sebastian on HNFor someone looking for a GraphQL solution, which benefits does EdgeDB have over https://github.com/graphile/postgraphile ?
kawera on HN
Why it is slower than vanilla Postgres in benchmarks
From 1 comment
Is it correct to say that EdgeDB is an attempt to make Postgres better in terms of query language and abstractions? By "better" I mean the idea of being more flexible and…
YohAsakura on HN
Alternatives named
Hasura
From 1 comment
Which benefits does EdgeDB have over Hasura which isn't built on top of PostgreSQL but as a layer that runs on top of it and exposes a GraphQL API along with access control,…
sebastian on HN
PostGraphile
From 1 comment
For someone looking for a GraphQL solution, which benefits does EdgeDB have over https://github.com/graphile/postgraphile ?
kawera on HN
Neo4j
From 1 comment
I wonder how this stacks up against a dedicated graph database like Neo4J. Are arbitray-depth graph queries a design goal, or are the nested results just for optimizing network…
scribu on HN
CockroachDB
From 1 comment
How do you think you compare to Cockroach? Besides the query semantics, I’m curious about the depth of the thought around cross region / cross continent and horizontal scaling…
zilchers on HN