Quiver
Languages and libraries
graphql server
SHOW HN2018
How HN took it
2 positive, 2 neutral or asking, 1 mixed, 6 critical, out of 11 comments about the project. Thread score -0.30.
Idea: 1 for, 2 againstPerformance: 1 for, 2 againstPricing: 0 for, 1 againstExecution: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful for internal GraphQL APIs
From 1 comment
Quiver looks interesting, congrats on launching! It seems like it will be very useful for internal GraphQL APIs. It does bring up something that I think the GraphQL community…
ianstormtaylor on HN
Saves servers if it speeds up traffic handling
From 1 comment
If it allows you to run 5 fewer servers to handle your traffic, then very probably, yes.
CGamesPlay on HN
Objections
Only allows pre-defined queries, limiting public APIs
From 3 comments
Quiver looks interesting, congrats on launching! It seems like it will be very useful for internal GraphQL APIs. It does bring up something that I think the GraphQL community…
ianstormtaylor on HNYour second bullet point, "Only allow certain queries from a document store", seems to be a major, major limitation, and directly contrary to one of the principal design goals of…
hn_throwaway_99 on HNThanks for the response! I agree, having queries live in the client is a great goal for DX on the frontend. The ideal being to have them co-located right with the components that…
ianstormtaylor on HN
Benchmarks don't reflect real production bottlenecks, which are databases and external services
From 2 comments
Open source lead at Apollo here. Syrus is correct that it will have about the same performance as Node in these particular benchmarks. We are working on performance improvements…
djmashko2 on HN+1 to this. These kinds of benchmarks of the actual execution of a server are almost never useful for actual production loads—it's always going to be the database or external…
ianstormtaylor on HN
Persisted queries hurt co-location and optimization flexibility
From 1 comment
Thanks for the response! I agree, having queries live in the client is a great goal for DX on the frontend. The ideal being to have them co-located right with the components that…
ianstormtaylor on HN
Requests
Add a cache middleware that registers dynamic queries automatically
From 1 comment
I think it would be fine to implement a cache middleware that transparently registered new queries and assigned them an ID. I wonder if this is on the roadmap for v2.
CGamesPlay on HN
Add Apollo Server to benchmarks
From 2 comments
why wasn't apollo server included in the benchmarks ?
angryasian on HNApollo-Server and Express-GraphQL are using the same GraphQL engine under the hood (the default GraphQL-js engine), so the difference from the currently benchmarked Node server…
syrusakbary on HN
Questions
Is it just caching?
From 1 comment
Sooo Quiver is just caching?
biznickman on HN
Is it worth $200/month?
From 1 comment
And this is worth $200/month?
Finnucane on HN
Why not include Apollo Server in benchmarks?
From 1 comment
why wasn't apollo server included in the benchmarks ?
angryasian on HN
Alternatives named
Juniper (Rust GraphQL library)
From 1 comment
Juniper - GraphQL library (+ Server if you want it to) written in Rust: https://github.com/graphql-rust/juniper We’re using Juniper in production as a central API for other…
KenanSulayman on HN
Apollo Server
From 1 comment
Open source lead at Apollo here. Syrus is correct that it will have about the same performance as Node in these particular benchmarks. We are working on performance improvements…
djmashko2 on HN
Relay Modern
From 1 comment
Relay Modern allows co-located queries with components. I don’t understand your concerns about performance or security. GraphQL should only expose the fields you can fetch in a…
underwater on HN