Apify Reviews

GraphQL Cache Reviews

Apify mentions (46)

• Google's News API has been gone since 2016, and people still search for it

  That runs News Scraper on Apify, which is the same forty lines plus the parts that are Tedious rather than hard: both feeds, the nested publisher element, the date Normalisation, and deduplication. - Source: dev.to / 17 days ago

• WHOIS is gone, RDAP replaced it, and a 404 does not mean what you think

  That runs an Apify Actor I maintain, Domain Scraper, because the Tedious parts are the RDAP bootstrap, the vcard unpacking and the provider Fingerprinting rather than the HTTP call. If you would rather do it yourself, Https://rdap.org/domain/ is the whole API and it needs no key. - Source: dev.to / 17 days ago

• How I Turned Canadian Open Government Data Into a Live Licence-Verification Site + API (Build Log, 2026)

  Data collection: Apify actors, one per source, that scrape the open-data endpoints and normalize them. Quebec RBQ ships a daily bulk CSV (inside a 10.8 MB zip, ~924k rows that dedupe to ~54k active licences). Ontario HCRA has no bulk file — it's an internal JSON API behind the public registry. - Source: dev.to / about 1 month ago

• How to Track US Startup Funding Rounds in Real Time (Before TechCrunch Writes About Them)

  Create a free Apify account and grab your API token from Settings → API & Integrations. - Source: dev.to / about 1 month ago

• I built a Claude Code skill that finds customers, not competitors, on Reddit & LinkedIn

  BYOK. It runs on your own Apify token. No shared keys, no lock-in, no licensing chokepoint — a lesson the whole "Proxycurl shut down and stranded everyone" saga taught the space. - 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 3 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 / over 4 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 / over 4 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 5 years ago