No GraphQL Cache videos yet. You could help us improve this page by suggesting one.
GraphQL Cache might be a bit more popular than EdgeDB. We know about 4 links to it since March 2021 and only 4 links to EdgeDB. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / 9 months ago
See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / 9 months ago
>relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all intended readabilty when you have SELECT col1, col2 FROM (SELECT * FROM ... WHERE 1=0 AND ... Which is what edgeDB is trying to solve. [0]https://edgedb.com/. - Source: Hacker News / about 1 year ago
You have to do your own optimiser to avoid, for instance, the N+1 query problem. (Just Google that, plenty of explanations around.) Many GraphQL frameworks have a “naive” subquery implementation that performs N individual subqueries. You either have to override this for each parent/child pairing, or bolt something on the back to delay all the “SELECT * FROM tbl_subquery WHERE id = ?” operations and convert them... - Source: Hacker News / about 2 years ago
'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 1 year ago
> Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / about 2 years ago
> Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / about 2 years ago
This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / almost 3 years ago
Datahike - A durable datalog database adaptable for distribution.
WunderGraph - Save 2-4 weeks / 90% of the code building web apps by automating API integrations and security.
Datomic - The fully transactional, cloud-ready, distributed database
Ehcache - Java's most widely used cache.
Oracle TimesTen - TimesTen is an in-memory, relational database management system with persistence and...
Apache Ignite - high-performance, integrated and distributed in-memory platform for computing and transacting on...