Datomic VS GraphQL Cache

Datomic

The fully transactional, cloud-ready, distributed database

GraphQL provides a complete description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.

Landing page //
2023-09-14

Landing page //
2023-08-29

KotlinConf 2018 - Datomic: The Most Innovative DB You've Never Heard Of by August Lilleaas

GraphQL Cache videos

No GraphQL Cache videos yet. You could help us improve this page by suggesting one.

+ Add video

Category Popularity

0-100% (relative to Datomic and GraphQL Cache)

Datomic

GraphQL Cache

Databases

88 88%

Databases

12% 12

NoSQL Databases

85 85%

NoSQL Databases

15% 15

Network & Admin

100 100%

Network & Admin

0% 0

Key-Value Database

0 0%

Key-Value Database

100% 100

User comments

Share your experience with using Datomic and GraphQL Cache. For example, how are they different and which one is better?

Social recommendations and mentions

Based on our record, GraphQL Cache seems to be more popular. It has been mentiond 4 times since March 2021. 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.

Datomic mentions (0)

We have not tracked any mentions of Datomic yet. Tracking of Datomic recommendations started around Mar 2021.

GraphQL Cache mentions (4)

What are the Differences between GQL and REST?
'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 1 year ago
GraphQL Is a Trap?
> 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
GraphQL Is a Trap?
> 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
Designing a URL-based query syntax for GraphQL
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 / about 3 years ago