ArangoDB Reviews

GraphQL Cache Reviews

ArangoDB mentions (6)

• MongoDB takes a swing at PostgreSQL after claiming wins against rival

  If you like the document db idea there are a lot of choices, especially https://arangodb.com/ which I think gets little attention because people who use it see it as a secret weapon. Too bad about the license though. Also https://couchdb.apache.org/ and https://developer.marklogic.com/. - Source: Hacker News / 8 months ago

• Which Database is Perfect for You? A Comprehensive Guide to MySQL, PostgreSQL, NoSQL, and More

  ArangoDB is a multi-model database that supports document, key-value, and graph data models with a unified query language. - Source: dev.to / 10 months ago

• Demonstrating ArangoDB VelocyPack: A High-Performance Binary Data Format

  In modern databases, efficient data serialization and deserialization are paramount to achieving high performance. ArangoDB, a multi-model database, addresses this need with its innovative binary data format, VelocyPack. This article delves into the intricacies of VelocyPack, demonstrating its advantages, usage, and how it enhances the performance of ArangoDB with code examples in Java and Rust. - Source: dev.to / 11 months ago

• How to choose the right type of database

  ArangoDB: A native multi-model database, it offers flexibility for documents, graphs, and key-values. This versatility makes it suitable for applications requiring a combination of these data models. - Source: dev.to / about 1 year ago

• Spidergram is a collection of tools my company Autogram has built or enabled over the past several years to support our work to automate content inventories for large websites: it's part web crawler, part domain model, and part mad science. We released the first public beta today.

  ArangoDB, a "multi-modal" database engine that stores arbitrary JSON documents like MongoDB, key/value data like Redis, and graph relationships like Neo4j — and lets you leverage all three kinds of data in a single query. Source: over 2 years ago

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 2 years 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 / almost 3 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 / almost 3 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 / almost 4 years ago