What our Users say about WunderGraph
Don't take our word, listen to what our Community has to say about WunderGraph. There were no incentives and we didn't ask for "nice feedback", just their honest opinion.
The modern software stack quickly becomes a polyglot of software systems, stacks, and technologies in complex projects. The need for faster deadlines and more complex requirements leads to cluttered or unorganized data models and architecture. As business directives change or pivot, so does the need for further development of integrations, adaptations, and internal software services. A single universal graph using GraphQL helped alleviate some of this by allowing DDD to evolve a system without breaking changes through deprecations when following GraphQL best practices. Along with this came other issues when attempting to expose GraphQL to the public with several security issues, which Jens lays out here nicely. We just finished rebuilding our entire company's operating platform, with WunderGraph playing a critical role. Our front-end-to-back-end interactions require complex integrations and flexibility to adjust operations for the application clients without deploying back-end changes in our multi-tenant engine. Without WunderGraph, we would not have been able to develop two platforms for production simultaneously without hindering progress or launch. We created operations against the platform engine to produce two different products leveraging the same core platform. We're excited to see what we can achieve working with WG in the future to create better systems faster.
Excited to see this and congrats to the team! I've been huge fan of GraphQL for a while and have checked out all of the major players. A big one I've used in the past is Hasura. It's refreshing to see Wundergraph's approach because it appears they've managed to couple the generated client and server in a way that assures your code is correct (beyond just having type-safe queries) while maintaining the flexibility of having multiple data sources configured with code. There's no wasted effort here. Can't wait to see where they take this - if their blog is any indication, they will continue to add innovation in this space. You can tell Jens has put a massive amount of thought into what GraphQL is best used for and what the DX should be.
I've played around with several graphql autogenerators like Hasura. But there was always something missing. Wundergraph's amazing approach at creating rest apis from graphql queries was a breath of fresh air and a much needed development pattern. I've come to realise that what has been missing till date was the developer experience Wundergraph has managed to create. Super excited for the future of this tool.
Congratulations Wundergraph team. I've been exploring Wundergraph as an alternative to another service I'm using and I have to say that it looks quite promising. Coming from a FrontEnd background, Wundergraph really simplify things for me, not only by providing me with a client that is 100% TypeSafe but by centralizing my APIs and the way I integrate them in my project, it's really neat. I find Wundergraph to have the best of both worlds, it gives you tools you need to handle authentication/authorization, file storage but it also give you all the flexibility you need to do things your way.
I'm really excited with Wundergraph and how it could help me with the project I'm working on.
I have been, and remain, very bullish on this project. The graphql community grew fast and the dust is still settling, when it finally does, WG will emerge as a standard. Calmly saving developers massive amounts of time and helping them start from a security minded foundation of best practices. I've worked on a wundergraph/svelte app at a large legal startup and am now beyond excited to champion it's adoption in the web3 space in my new role at Heir labs . Absolutely thrilled to see the big day has finally come, congrats to all of you at WG for tackling a very difficult problem with diligence and discipline. It's hard to keep your eye on the problem that needs to be solved when working on an ambitious projects and that's exactly what you guys have done, congrats! Also Jens is one the most brilliant, productive, and humble people I've met . I can't wait to watch the community grow and contribute in a new way now that it is open source! Best of luck too all of you!
As an agency we've built several projects with GraphQL, with either Hasura or GraphQL Nexus powered APIs. We love the declarative syntax of GraphQL, and Hasura is very approachable, but I had some underlying architecture concerns for more serious projects (that Jens did a great job of summarising in one of his blog posts. WunderGraph basically gives you the best of both worlds, a more secure way of using GraphQL without losing the convenience & DX. WunderGraph also has an interesting take on GraphQL subscriptions, as described here. At a glance WunderGraph and Hasura seem to be solving some of the same problems - i.e. aggregating external GraphQL & REST APIs, generating an API for you over your own database... BUT - WunderGraph generates your own custom SDK (fully typesafe) for use in your frontend code. This super tight coupling makes for a really great developer experience. Hasura is less opinionated in that way, you can use any GraphQL client library and codegen/introspection tooling - but you have to wire it all together yourself. The Hasura console UI also feels frustrating to use at times (e.g. bulk editing permissions), and testing your schema programatically is cumbersome. You can do advanced RBAC with WunderGraph, writing queries/mutations ("operations") for each role, and custom logic is possible via hooks that you can write in typescript. It all just feels very well thought out and extensible. As an agency you want to use consistent tooling across different client projects to minimise technical debt and maintenance effort, but that tooling also has to be super flexible to deal with different client requirements. It's early days for us with WunderGraph but the maintainers are very approachable and it is already feeling like a safe 'bet' to me
I started using Wundergraph as a backend service for our recently launched platform in February of this year. I found the usage to be simple and easy to understand, but development and deployment was rough at times, earlier this year there were bugs on some of the common use cases. The team has been very responsive and those issues have been resolved. Two major changes have pushed this framework into a really mature place. One was a recent rewrite around custom resolvers, which allows for adding business logic in between GraphQL calls. The other is going fully open source. Despite some initial challenges with the framework, I can't deny that Jens understands the problem domain probably better than anyone else in the world. Glad to see so many issues like authentication and API interconnectivity solved in a production ready way. I'm getting out of the box functionality that I used to depend on entire teams for. The depth of auth implementation, from one line config of Auth0 all the way down to per-operation RBAC is the shining example of how well this framework is architected. Can't wait to see the continued development and growth from their team!
Congratulations, Team Wundergraph. I've been using wundergraph for last couple of months in some hobby projects and also using it on my startup. It boost my team's productivity and API development process easy to easier. In the beginning, I had some doubts and problems on some places, but the community and wundergraph team! They helped me instantly. And overall experience is really impressive. Wundergraph has become a part of our tech stack, and we wish the Jens and the full team, Best of luck. Will definitely use wundergraph in our future projects too.
I had great developer experience with wundergraph. Best part of using wundergraph is it can take multiple data sources, generates graphql operations and Rest API endpoints. We can change / extend operation functionalities using hooks (preResolve, postResolve and custom). When sometimes none of the data source meets our exact requirement, we can create custom operations. It has one bonus feature for developers like me who use postman extensively for API testing, It generates postman collection with all api endpoints. Since now it is open source. I would like to contribute in codebse. Kudos team for great product.
Wundergraph is a awesome tool for both backend and frontend engineers. You can connect third party APIs easily on backend and the best part is it generates a type safe client with all queries and mutations which will save front end a ton of time. Congratulations