WunderGraph Blog

The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions (https://wundergraph.com) and I benefit from the networking and communication abilities of Stefan, while I answer all technical questions. Tldr, I highly recommend to team up with people who complement your skills.

Wundergraph (https://wundergraph.com) | REMOTE (Anywhere) Wundergraph is best way to interact with API's. You can consume any number of API's and merge it into one single API— we are changing how we collaborate and interact with API's. Built-in Authentication, Authorization and Caching, easily customizable with hooks in every language, and secure and highly performant by design Or, put another way: We'll automate about 80% of your API related tasks. We are currently hiring for these roles: * Engineering Manager * Senior Fullstack Developer * Senior Frontend Developer * Product Marketer Our stack is mainly React, TypeScript, GraphQl, Redux and Wundergraph. We are a product driven startup and looking for individuals who are passionate about APIs and changing the norm for the better. Joining Wundergraph means jumping into the drivers seat of a F1 race car. You'll get plenty of experience and resources and the potential to leave a huge impact in an early-stage solution that is changing how developers view and interact with API's. The problems we are solving are unsolved, open ended and in need of creative minds to help us change the future of APIs. Perks of working at Wundergraph Competitive compensation Premium access to Wundergraph Unlimited PTO Company stock options Fully Remote More info on all positions: https://past-gorgonzola-d38.notion.site/Wundergraph-Job-Board-39aed110… (no recruiters/agencies…

++ on the Guild. They are leaders in the GraphQL tooling space and offer a wide array of solutions. I'd also like to give a nod to Wundergraph and their Apollo Alternative. We were given early access to Cosmo[0] and so far are very happy with it. They have their own GoLang based router that is independent of Apollo, works with v1 and v2 of federation, and works with subscriptions. Comes with Studio, a CLI tool, and a OTEL Collector. So far it's been great for us at our org. [0]: https://wundergraph.com/cosmo

How is this different from WunderGraph? https://wundergraph.com/

Jens and team, congratulations! For the rest of the HN/YC community, give a try to Wundergraph --> https://wundergraph.com A package manager for APIs is the way to go.

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 (https://wundergraph.com/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.

ha! Just wait until it's wrapped with https://wundergraph.com/

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: https://wundergraph.com/blog/the_complete_graphql_security_guide_fixin… 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: https://wundergraph.com/blog/deprecate_graphql_subscriptions_over_webs… 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…

WunderGraph - Senior or Staff Platform Engineer/ Senior Typescript Engineer/ Full Stack- REMOTE-EMEA Hi. I am Alex, I am scaling the team at WunderGraph. We are a remote, global, series A start up, backed by eBay to continue innovation in the API Management Space. Currently 23 people, we plan on scaling our team, and have roles across: Senior Platform Engineer: https://wundergraph.com/jobs?ashby_jid=d8608bb4-eef7-4b43-b04b-0053ba3… Senior Typescript Engineer - https://wundergraph.com/jobs?ashby_jid=97443b40-84cd-4d9e-8598-0d5d19c… We are also looking for 2 BDRs to join us in Miami in a hybrid role. Culturally, these opportunities would fit someone that prefers to work in a no BS culture, highly collaborative, high performance, with big scope for impact, alongside a global team. Please apply if you believe we can grow together.

WunderGraph | Multiple Roles | REMOTE | Full-Time WunderGraph (growing global customer base, 70K weekly downloads and growing) APIs are the backbone of every modern organization. But building and maintaining APIs is hard, especially when you'd like to scale API development across multiple teams. The key to success is collaboration. Our mission is to take API collaboration to the next level. With Cosmo, we're give platform teams a solution to provide a self-service API Developer Platform to their teams. We believe that Open Source is the key ingredient to become the number one solution for API Development and Collaboration. The project is completely open-source. You will be an integral member of an expanding team at a VC-funded startup with a dynamic mission to innovate and transform the field of GraphQL Federation. Apply here: https://wundergraph.com/jobs#open-positions

Since you're in here, if I can recommend: sync.Pool with non-fixed-size objects is a source of many problems. https://wundergraph.com/blog/golang-sync-pool as a decent overview, and https://github.com/yarpc/yarpc-go/issues/2355 has been my recent plague. If you browse around Go's stdlib use of sync.Pool, you'll see a variety of tiered pools with fixed sizes, and many drop anything over a large enough size (sometimes gigantic! as much as 16KB!): https://cs.opensource.google/go/go/+/refs/tags/go1.24.0:src/net/http/s… It's a pretty well-established gotcha, sadly, and https://github.com/teivah/100-go-mistakes/blob/master/src/12-optimizat… falls right into it.

Since I'm not going to type a novel here is an example: https://wundergraph.com/blog/the_complete_graphql_security_guide_fixin… Also look at hackerone: https://hackerone.com/hacktivity?querystring=graphql

I am a big fan WunderGraph and I think it's a very promising project. Some solid design choices. What I like: - customization in TypeScript but running the core gateway in Go for performance - nicely typed auto-generated clients - cross-API joins to compose APIs - their approach of using GraphQL as schema language but not exposing it to clients https://wundergraph.com/blog/graphql_is_not_meant_to_be_exposed_over_t… However, the project is still very fresh and not mature. Their current OpenAPI spec introspection is severely lacking on "real world" oas and many of the response structures won't parse properly and fallback to generic JSON. Related to this the docs are sparse so I was unable to find how one can customize/extend/override the auto-generated schemas. But they are actively working on it so I believe they will solve this. Sadly I need something right now and GraphQL Mesh offers very similar capabilities with much more mature OpenAPI parser which can even handle upcoming @oneOf tagged unions. https://the-guild.dev/graphql/envelop/docs/guides/using-graphql-featur… GraphQL Mesh seems more operational ready with ready-to-use OpenTelemetry and Prometheus plugins. And it can be deployed easily to serverless. I really like WunderGraph approach and architecture so I hope I can pick it for a future project.