Show HN: EdgeDB 1.0
This seems kind of cool, but honestly the benefits described don&#x27;t really solve actual problems I&#x27;ve run into in development. The overall article reads like marketing talk and doesn&#x27;t actually describe concretely why it&#x27;s better than existing solutions. For something as core as a database I would expect more rigorous descriptions and benchmarks.<p>&gt; We shall do better than SQL 
The EdgeQL language looks cool, and I&#x27;m sure querying via a graph structure makes certain problems easier in some use cases. However as much as people have complained about SQL, it&#x27;s just so ubiquitous there needs to be a very good reason to switch away from it. Not having to write joins isn&#x27;t really a good enough reason, in my opinion.<p>&gt; The true source of truth
I&#x27;m not sure why this means EdgeDB is better. Tons of applications use a traditional or cloud SQL database as the source of truth right now. This section seems to imply with microservices you no longer have a single source of truth. But if they&#x27;re trying to say a microservice system should instead us a single common database that breaks separation of concerns and moves us into an annoying situation where you have a bunch of services communicating via a shared database.<p>&gt; Not just a database server 
It sounds like they have a solid client, which is awesome.<p>&gt; Cloud-ready database APIs 
&gt; The vast scale of modern application deployments requires that inelastic computing resources are managed very carefully. Until cloud-native databases reach complete functional and performance parity with traditional databases, we will have to contend with the fact that the database is a scarce resource.<p>This used to be true, but is definitely no longer true. Cloud-native databases are everywhere and incredibly common. See any major cloud, <a href="https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cockroachlabs.com&#x2F;</a>, or any of the tons of other database solutions.<p>It&#x27;s great to see a new database coming out - innovation in the space is super important. However this announcement reads like marketing speak, and is light on the details. When I see a new product I want to hear things like:
- about how it scales
- what the architecture is
- why is it stable and trust-worth enough to put my data on
- is it multi-node? How did they make it serializable?
- how fast is it? Performance is super important.<p>Based on their website it seems like a thin skin over postgresql. If that&#x27;s the case I&#x27;ll just use postgresql. If it&#x27;s a clustered new and advanced database, then I&#x27;ll be wary about trusting it for anything real.