GraphQL Portal is an open-source API aggregator. You can connect any data-source or API using one of our 30 connectors (REST, Swagger, SOAP, GraphQL, gRPC, Contentful, Salesforce, SAP etc...). Portal will then generate a GraphQL Schema and endpoint for you. It manages back-end caching, authentication, throttling, quotas. It's also shipped with a visual dashboard making it easier to setup and configure the gateway.
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.
'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 2 years 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 / almost 3 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 / almost 3 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 4 years ago
OneGraph - OneGraph is a GraphQL service that wraps and connects the internet's SaaS APIs. Build integrations to Stripe, Intercom, Salesforce, Zendesk, GMail, and more 10-100x faster with OneGraph.
Ehcache - Java's most widely used cache.
StepZen - A low code way to create GraphQL APIs for any backend—REST, SQL, NoSQL, SOAP/XML. Deploy a single or federated graph to StepZen's cloud and run with built-in parallel execution, security for APIs and data, and performance & reliability optimizations.
Apache Ignite - high-performance, integrated and distributed in-memory platform for computing and transacting on...
Apigee - Intelligent and complete API platform
Hazelcast - Clustering and highly scalable data distribution platform for Java