wundergraph-demo
transferred-stepzen-schemas
wundergraph-demo | transferred-stepzen-schemas | |
---|---|---|
12 | 22 | |
68 | 16 | |
- | - | |
0.0 | 0.0 | |
almost 2 years ago | over 2 years ago | |
TypeScript | JavaScript | |
- | 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.
transferred-stepzen-schemas
-
How to connect Stepzen Graphql queries to supabase(Postgres database)?
Go to stepzen.com and click on the start for free button.
-
GraphQL and RxDB
Either way, I'm not too familiar with RxDB but looking at the docs you can also use StepZen to create the GraphQL layer that you use for replication. With StepZen you can build and deploy a GraphQL API based on multiple datasources (including MSSQL) in minutes. That way you only have to worry about building the logic that pulls and push replicates data to and from GraphQL. How you structure the MSSQL database would become the most important part of this project, to ensure a smooth replication.
-
Upload Schema like FaunaDB
There are multiple ways to get a GraphQL API on top off a Postgres database. If you want to have a GraphQL abstraction layer that runs as a hosted service and needs almost no code, have a look at StepZen. You can build a GraphQL API for the Postgres database by following the docs here. StepZen introspects the database (using stepzen import postgresql) and let it create the schema for you based on all the tables and columns of your database. Including a set of queries to get started with.
-
What's the best alternative to Apollo studio?
If you’re looking for a managed service, have a look atStepZen. You can combine multiple GraphQL schemas into one cloud GraphQL API. Instead of writing a gateway yourself, you can use SDL to merge different schemas. Besides GraphQL APIs you can also “federate” other data sources like SQL or REST
-
Are there actually better alternatives than Apollo server?
There are many of them, including StepZen which is language/framework agnostic and let you create a GraphQL server with GraphQL SDL only - in a declarative way
-
Join multiple GraphQL APIs without Schema Stitching or Federation
I’ve seen more products letting you join/merge GraphQL schemas independent of schema stitching or federation. Have a look at GraphQL Mesh or StepZen.
-
What's next?
You can save yourself the hassle of having to build a GraphQL server, resolvers and database connections with StepZen (https://stepzen.com). It’s a product that is based solely on GraphQL SDL and you set the database connections with directives. Also, you can use it to connect other APIs
-
How My View on Open Source Has Changed
There is one thing I can say for sure: I love the spirit of open source. I've had a wonderful time working with open source communities of different sizes (e.g. Seneca-CDOT, StepZen, Appwrite, and Zulip). Fortunately, all of them are fantastic and patient with beginners.
-
Apollo Datasource Rest - am i using it right?
If the only thing you're trying to do is converting a REST API to GraphQL, you should have a look at https://stepzen.com/
-
Learn GraphQL through Contributing to StepZen
StepZen filed an issue about writing a GraphQL schema to integrate SpaceX REST API into their React application. I found this as an excellent opportunity for me to learn GraphQL.
What are some alternatives?
blog-django-graphql-hasura - An example implementation of a Django Graphene GraphQL API meshed with Hasura Remote Schemas for auth.
api - Sorare API documentation
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
supabase - The open source Firebase alternative. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
graphql-zeus - GraphQL client and GraphQL code generator with GraphQL autocomplete library generation ⚡⚡⚡ for browser,nodejs and react native ( apollo compatible )
faunadb-js - Javascript driver for Fauna v4 (deprecated)
gqless - a GraphQL client without queries
tailwind-nextjs-starter-blog - This is a Next.js, Tailwind CSS blogging starter template. Comes out of the box configured with the latest technologies to make technical writing a breeze. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.
great-bear-hasura - A food delivery API example using Hasura
nextjs-tailwind-ionic-capacitor-starter - A starting point for building an iOS, Android, and Progressive Web App with Tailwind CSS, React w/ Next.js, Ionic Framework, and Capacitor
federation-subscription-tools - A set of demonstration utilities to facilitate GraphQL subscription usage alongside a federated data graph
tokens