Backend

EdgeDB is underrated.

Graph-relational links, computed fields, constraints on arbitrary expressions, set theory-based, automated deterministic migrations via CLI, a generated TypeScript query builder instead of an ORM…

Architecture and developer experience are extremely well thought out.

EdgeDB is underrated.

Graph-relational links, computed fields, constraints on arbitrary expressions, set theory-based, automated deterministic migrations via CLI, a generated TypeScript query builder instead of an ORM…

Architecture and developer experience are extremely well thought out.

https://www.edgedb.com

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

These kinda things are great for simple crud apps but as soon as you have to do complicated/more performant queries, they fall apart

That's what I'd say about traditional SQL databases. Don't even want to think about the JOIN clauses that would be involved.

In EdgeDB you can go as deep as you want. It's all handled and optimized for you.

Considering New Roles | Prev 
SushiSwap | Prev Web2 Senior Engineer/Architect | All opinions are my own

That's what I'd say about traditional SQL databases. Don't even want to think about the JOIN clauses that would be involved.

In EdgeDB you can go as deep as you want. It's all handled and optimized for you.

https://www.edgedb.com/docs/edgeql/select#subqueries

https://www.edgedb.com/docs/edgeql/insert#nested-inserts