Fills a vacuum in this space, thank you so much for sharing. Coolest of times for devs and clients: Wundergraph enables front-end devs to perform like full-stackers, see the larger picture and begin to influence and control the back-end. Watch out back-enders, front-enders are gonna eat your lunch!
I tell my friends to watch your video. In my college everyone likes your typescript videos. These are so unique videos. Would love to know your journey. I.e how you started and how you reached where you are right know. These videos Gives me inspiration to code. I'm not that great on coding. But I'm sure i can get better at it...
Thanks! I'll have more a think about a journey video. I'd feel weird making it super self-centered. :) Thanks for asking. The best way to get better at coding is to keep coding, daily. And to work with other people and read other people's code.
Thanks for the great video as always! Continuing on with the GraphQL theme, I'd love to hear your thoughts on technologies like Postgraphile that allow you to map GraphQL queries to a single SQL query instead of relying on batching + multiple requests.
I like Hasura as well, and the Wundergraph team is on here, so maybe they can answer better, but from my perspective, Wundergraph has multiple data source aggregation, built in typescript code generation, and the server-side-only GraphQL model as distinguishing benefits. So... a lot.
I answered the question above as well, but trying to add some useful information here too. Translating between Database and API layer is one of the many problems to solve when building an application. Both Hasura and WunderGraph solve this problem. Both add a lot more on top of that, for example permissions etc... That said, Hasura draws a line where its responsibility stops, and that's right in front of the GraphQL API. Hasura directly exposes a GraphQL API and offers a few mechanisms, like whitelisting, to protect this API. WunderGraph on the other hand goes a fundamentally different way. We don't expose a GraphQL API because we believe nobody should expose GraphQL in the first place. Instead, we expose a secure and web compliant REST API, where Queries will be used via GET requests and mutations over POST. Hiding GraphQL behind a REST API doesn't just improve security, it comes with a lot of other benefits. For example, we can use the WunderGraph code generator to generate a client that is 100% type safe and works perfectly fine with the generate REST API. It doesn't just handle API access but also authentication and file uploads. Although I was mentioning REST a few times, the whole developer experience still feels like you're using GraphQL, just like you saw in the video from Jack. So, to sum it up. Other solutions provide an API. WunderGraph is the only tool to give you and end-to-end solution, from backend to frontend, without any additional dependencies or fiddling around.
React-Query makes it easier to do HTTP queries from the client (or the server during SSR). React Location is a router. Redux Toolkit is a helper library to make build Redux stores easier. And Relay is a framework that makes it easier to manage GraphQL requests.
Hi Jack. There are a lot of great tools coming out right now, but it's getting harder to figure out what's important and what's not. Also, I have no idea how much Wundergraph would add to the cost of running an application in production. Could you elaborate on your thoughts on this? ( Importance, Price )
It's a Go server, serving REST, which is going to mean that it can return more requests per second, which would reduce cost versus say Apollo server on Express, which is Node, plus it's having to interpret and validate each GraphQL request.
@6:26 you get rich autocomplete. I cant seem to get that? Is there an extension or setting I am missing, I do not think that is github auto pilot as its from the command space menu.
Yeah, we used it at the last job. I'm not 100% on the full Hasura feature set but I think Wundergraph has advantages in being able to aggregate more data sources, do automatic typing, and also the server-side only GraphQL model.
@@jherr Agree, WG is more generalized, they are API-oriented, while Hasura is Database-oriented (Postgres in specific), in terms of security and authorization/authentication, caching side, WG is doing a great job, I checked a link on their site discussing the difference vs hasura, they are probably biased in this comparison. Thanks Jack for the demo .
This is like a self run firebase / amplify data application layer. Very interesting - thank you very much for covering this!
Never heard about wundergraph before, I like it's more precise on the client side than using urql with Hasura. Greetings Jack.
Fills a vacuum in this space, thank you so much for sharing. Coolest of times for devs and clients: Wundergraph enables front-end devs to perform like full-stackers, see the larger picture and begin to influence and control the back-end. Watch out back-enders, front-enders are gonna eat your lunch!
This is the most insane tool I've seen, thanks for making a video about it
I tell my friends to watch your video. In my college everyone likes your typescript videos. These are so unique videos. Would love to know your journey. I.e how you started and how you reached where you are right know. These videos Gives me inspiration to code. I'm not that great on coding. But I'm sure i can get better at it...
Thanks! I'll have more a think about a journey video. I'd feel weird making it super self-centered. :) Thanks for asking. The best way to get better at coding is to keep coding, daily. And to work with other people and read other people's code.
Thanks for the great video as always! Continuing on with the GraphQL theme, I'd love to hear your thoughts on technologies like Postgraphile that allow you to map GraphQL queries to a single SQL query instead of relying on batching + multiple requests.
I'll check that out!
Thank you for the video! Really interesting approach, better and faster than pure prisma + any gql server
Interestingly, the tool chain reminds my in many ways of Django except for the client creation..
Cool. I have framework vertigo. The really smart people keep making things "easier" for me.
Thank you for posting this amazing content.
BTW - I never thought that there were green trees and flowers during winter in Oregon ;)
Hahah, yeah, my green screen plate is from the summer. :) It certainly will not be looking like that next week as we hopefully, get covered in snow.
This is nice one, but if you can look and make video on Keystone JS v6 it would be great for the TS community.
second on keystone js new GA version
I use Hasura. Why should I use Wundergraph? Or these two are different?
Same question here
I like Hasura as well, and the Wundergraph team is on here, so maybe they can answer better, but from my perspective, Wundergraph has multiple data source aggregation, built in typescript code generation, and the server-side-only GraphQL model as distinguishing benefits. So... a lot.
I think one of WG pros is not exposing the graphql endpoint when invoked for security purposes, if understood well.
I answered the question above as well, but trying to add some useful information here too. Translating between Database and API layer is one of the many problems to solve when building an application. Both Hasura and WunderGraph solve this problem. Both add a lot more on top of that, for example permissions etc... That said, Hasura draws a line where its responsibility stops, and that's right in front of the GraphQL API. Hasura directly exposes a GraphQL API and offers a few mechanisms, like whitelisting, to protect this API. WunderGraph on the other hand goes a fundamentally different way. We don't expose a GraphQL API because we believe nobody should expose GraphQL in the first place. Instead, we expose a secure and web compliant REST API, where Queries will be used via GET requests and mutations over POST. Hiding GraphQL behind a REST API doesn't just improve security, it comes with a lot of other benefits. For example, we can use the WunderGraph code generator to generate a client that is 100% type safe and works perfectly fine with the generate REST API. It doesn't just handle API access but also authentication and file uploads. Although I was mentioning REST a few times, the whole developer experience still feels like you're using GraphQL, just like you saw in the video from Jack. So, to sum it up. Other solutions provide an API. WunderGraph is the only tool to give you and end-to-end solution, from backend to frontend, without any additional dependencies or fiddling around.
Nicely done!
What is the difference between React-Query, React Location, Redux Toolkit, and Relay-GraphQL? Can we have the series on all of them in the next year?
React-Query makes it easier to do HTTP queries from the client (or the server during SSR). React Location is a router. Redux Toolkit is a helper library to make build Redux stores easier. And Relay is a framework that makes it easier to manage GraphQL requests.
Hi jack! Please make video on graphql vs REST. I'm totally confused which is good. I want to hear from you.
Hi Jack. There are a lot of great tools coming out right now, but it's getting harder to figure out what's important and what's not. Also, I have no idea how much Wundergraph would add to the cost of running an application in production. Could you elaborate on your thoughts on this? ( Importance, Price )
It's a Go server, serving REST, which is going to mean that it can return more requests per second, which would reduce cost versus say Apollo server on Express, which is Node, plus it's having to interpret and validate each GraphQL request.
Hi Jack Herrington
what is the better option? wundergraph or supabase
So you're the guy who wrote those vim plugins. Cool.
No, not that I'm aware of. I use vim now and again, but I'm a VS Code person, and have never written a vim plugin.
@@jherr Oops, really sorry about that. Now that I've looked him up, it's another Herrington.😶.
@@mhmmdshaz98 Huh, ok. Not a lot of Herringtons out there. :) Lots of Harringtons though.
Also, he too works with TypeScript stuff, I've used his TS plugin. That's how I came to this confusion.😛.
Another great tutorial! I have one question please : which VSCODE theme are you using?
Night Wolf [dark] and Operator Mono
What are you using to write in freehand that syncs to your desktop? Is that an iOS app?
I use ScreenBrush and a tablet.
Thank you for this knowledge 🙏
@6:26 you get rich autocomplete. I cant seem to get that? Is there an extension or setting I am missing, I do not think that is github auto pilot as its from the command space menu.
That's the GraphQL extension looking at the GraphQL schema generated by Wundergraph.
Nice video, getting hooks from wundergraph is something like graphql codegen with react query, right !
Yes, but also it has mulit-source data aggregation and the server-side-only GraphQL model.
@@jherr Awesome, thanks 👍
one question please Jack, what intellisense/autocomplete and syntax highlighting tool is used in graphql queries file :)
That's GitHub Copilot.
@@jherr thanks 👍
Hi Jack, which ORM do you prefer using, prisma is the best for me,
Prisma is fantastic.
incredible video
Great content thank you Jack
this thing's sweet!
Can wundergraph (WG) be used with Hasura together, like Prisma used here ! i.e. feeding WG with the Hasura graphql endpoint to get the pros of WG.
Yes. You can front Hasura with Wundergraph since WG can consume GraphQL data sources.
Woah this is amazing
how do u get all that ineligent auto complete ?
GitHub Copilot
Woow First 😉🙌 😎 zs cool
Wait. have you also seen Hasura?
Yeah, we used it at the last job. I'm not 100% on the full Hasura feature set but I think Wundergraph has advantages in being able to aggregate more data sources, do automatic typing, and also the server-side only GraphQL model.
@@jherr gonna give it try. Great content btw
@@jherr Agree, WG is more generalized, they are API-oriented, while Hasura is Database-oriented (Postgres in specific), in terms of security and authorization/authentication, caching side, WG is doing a great job, I checked a link on their site discussing the difference vs hasura, they are probably biased in this comparison.
Thanks Jack for the demo .
Second😌
i think Hasura does a better job and doesn’t require all this TS
I guess I'm third)