Docker Hub Reviews

GraphQL Cache Reviews

Docker Hub mentions (355)

• Building a Mini DevOps Project

  Create Docker Hub account: https://hub.docker.com. - Source: dev.to / 4 days ago

• Docker Image creation and pushing to DockerHub (Step-by-Step!) 🐳

  Go to https://hub.docker.com/ and you’ll see your freshly pushed image under Repositories! - Source: dev.to / 10 days ago

• 🚀 Docker Image Creation and Pushing to DockerHub: Step-by-Step Guide

  Docker push your_dockerhub_username/my-docker-app:latest After successful push, you can visit: 👉 https://hub.docker.com/ And find your repository under your profile. - Source: dev.to / 10 days ago

• Jozu Hub–Your private, on-prem Hugging Face registry

  A container registry: You can use Jozu Hub, the GitHub Package registry, or DockerHub. This guide uses Jozu Hub, which includes model auditing features. - Source: dev.to / about 1 month ago

• Explaining Docker to My Mother

  Me: Not always! Just like a grocery store sells ingredients, Docker Hub is an online store where developers get pre-made images for their apps. - Source: dev.to / about 2 months 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 / about 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 / about 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