wundergraph-demo
next-rpc
wundergraph-demo | next-rpc | |
---|---|---|
12 | 4 | |
64 | 141 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
TypeScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wundergraph-demo
-
NextJS / React SSR: 21 Universal Data Fetching Patterns & Best Practices
If you want to follow along and experience these patterns yourself, you can clone this repository and play around.
-
GraphQL Subscriptions: Why we use SSE/Fetch over Websockets
Thanks to our GraphQL Operation Compiler, we're in a unique position that allows us to only send the "Operation Name" as well as the "Variables" to the server. This approach makes our GraphQL API much more secure as it hides it behind a JSON-RPC API. You can check out an example here, and we're also open sourcing the solution soon.
-
API Gateway - REST upon graphql
I've been working on this problem for a few years actually. What I came to realize is that 99% of all (GraphQL) APIs are private, meaning that we don't expose them to a 3rd party. One aspect of private GraphQL APIs that is almost always true is that the access patterns don't change at runtime, meaning that when deployed to production, the Operations don't change any more. What this means is that in production, we don't really need GraphQL. We don't benefit from GraphQL in production anymore, as we're not writing dynamic Operations. Instead, we could compile the GraphQL Operations that we need into a REST API. This step adds extra complexity, but reduced the attack surface and improves performance. To reduce the overhead, I've created a developer tool. WunderGraph! It compiles your GraphQL APIs into REST Endpoints and generates typesafe clients for them. The DX is still the same, you write GraphQL Operations and use a typesafe client. But behind the scenes, it's just REST. We even generate a Postman Collection, so you can easily share the generated API with your team. Here's a demo if you'd like to try it: https://github.com/wundergraph/wundergraph-demo We're open-sourcing the solution very soon! =)
-
An Inconsistent Truth: Next.js and Typesafety
Alternatively, you can also just run "wunderctl init --template nextjs-starter" to start with the NextJS template. (Obviously you need to install it first: yarn global add @wundergraph/wunderctl@latest)
We're going open source with this solution soon. So, any feedback is appreciated! You can also join our discord and shoot questions. =)
[0]: https://github.com/wundergraph/wundergraph-demo
-
Benchmark: Apollo Federation Gateway v1 vs v2 vs WunderGraph vs mercurius-js
WunderGraph: click here!
-
Apollo Federation 2 is here!!
It's already possible. Here's a demo: https://github.com/wundergraph/wundergraph-demo
-
Anyone implementing Schema Stitching over Apollo Federation?
Shameless plug, you can use Federation, Schema Stitching, REST APIs, etc. all together and even transition from one to the other, here's a demo: https://github.com/wundergraph/wundergraph-demo
- Merge 7 APIs into one unified JSON API and securely consume them from a NextJS application
- Show HN: Merge Apollo Federation, REST and GraphQL APIs Easily
- GitHub - wundergraph/wundergraph-demo: This Repository demonstrates how to combine 7 APIs (4 Apollo Federation SubGraphs, 1 REST, 1 standalone GraphQL, 1 Mock) into one unified GraphQL API which is then securely exposed as a JSON API to a NextJS Frontend.
next-rpc
-
An Inconsistent Truth: Next.js and Typesafety
I recommend "next-rpc" [1] which is a small library allows the nextjs client-side pages to call the API function using a type-checked function interface.
[1] https://github.com/Janpot/next-rpc
-
RPC in Next.js
When I was searching for JSON-RPC implementation for Node and Next. I've found this little gem, library next-rpc.
-
next-rpc makes exported functions from API routes directly accessible in components. Just import your API function and call it anywhere you want.
They've explained it well in the README: https://github.com/Janpot/next-rpc#why-this-library-is-needed
What are some alternatives?
blog-django-graphql-hasura - An example implementation of a Django Graphene GraphQL API meshed with Hasura Remote Schemas for auth.
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
SWR - React Hooks for Data Fetching
transferred-stepzen-schemas - A collection of importable GraphQL schemas for use with StepZen.
assert-combinators - Functional assertion combinators.
graphql-zeus - GraphQL client and GraphQL code generator with GraphQL autocomplete library generation âš¡âš¡âš¡ for browser,nodejs and react native ( apollo compatible )
refute - Refute module.
gqless - a GraphQL client without queries
gradual-typing-bib - A bibliography on Gradual Typing
great-bear-hasura - A food delivery API example using Hasura
federation-subscription-tools - A set of demonstration utilities to facilitate GraphQL subscription usage alongside a federated data graph