engine VS wundergraph

At Poozle (https://github.com/poozlehq/engine), I have created over 40+ OAuth apps and have dreaded every time we had to build them. Everything with Oauth is shit! You have to fill out numerous application details and finding the right scopes is a nightmare. Once you submit an application, there is often too much back-and-forth before the app is finally approved.

Possible Solution: I am considering to build an AI-powered browser extension for myself that automates the Oauth process with the following features:

1. *Auto-Fill:* Pre-fills 80% of the information required to create your app.

Hey, we are more than happy to pick. We already have an issue created https://github.com/poozlehq/engine/issues/125. Could you upvote here?

Hey r/TypeScript! Introducing Poozle, the open-source API integration platform built entirely in TypeScript. Say goodbye to glue code and simplify your API integration process. Customize with TypeScript extensions, and be part of our thriving community. Join us on GitHub https://github.com/poozlehq/engine and unleash the potential of TypeScript in API integration. Let's code together!

Hey, folks we are building an open-source unified API integration infrastructure platform. You can check us out here https://github.com/poozlehq/engine (https://poozle.dev). Do check us out.

We just launched Poozle (https://github.com/poozlehq/engine) which manages Oauth for different integrations and also provide unified data model.

Would love to get your feedback on the same.

Hey HN,

We are Manik, Harshith, and Manoj, the founders of Poozle (https://www.poozle.dev). Poozle is a single integration layer that brings together various SAAS APIs.

We provide a single GraphQL endpoint for all SAAS APIs, regardless of their protocols. Poozle makes it easy to build integrations for your app into services like GitHub, Jira, Salesforce, Pipedrive, Hubspot, and Gmail. To integrate any API, you typically need to read its documentation, implement its specific authentication, and make very specific calls to its servers. Although this may seem normal, it adds up and becomes time-consuming.

The three of us have done numerous integrations into these services for various startups over the years. As a result, we know how painful it can be, particularly when you need to coordinate data from multiple services.

Why GraphQL

We believe that GraphQL is a query language suitable for all APIs. We can express our data requirements succinctly, even between services, and let a single execution engine determine how to translate those requirements into specific API calls.

We have built a GraphQL service that knows how to communicate with each backend API we support, retrieving the exact data you need. Here is the link of out product demo:

[https://www.youtube.com/watch?v=uGIssARKYec&t]

We’d really appreciate your feedback on Poozle. We have a lot we want to improve on, and would love to hear where you want us to go next.

4. Observability: Our monitoring dashboard tracks API usage, latency, and error rates for quick incident detection.

We're still early, so we would love your feedback and opinion. Also, let us know if you need a specific API integrated.

Main Website: https://www.poozle.dev

I never really got graphql until I stumbled upon Wundergraph. (https://github.com/wundergraph/wundergraph). I have no affiliation with them except that I have been building an app with it. I'm honestly puzzled how it's not more popular. Maybe people are solving these problems in other ways? But I tried out a bunch of stuff: Vapor, Supabase, Hasura, etc. None of it simplifies building complex systems the way WG does.

I think their takes on graphql make sense: https://wundergraph.com/blog/graphql_is_not_meant_to_be_expo...

To demonstrate field usage metrics in Federation, I’ll be using WunderGraph Cosmo — a fully open source, fully self-hostable platform for Federation V1/V2 that is a drop in replacement for Apollo GraphOS.

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.

GraphQL Gateway is primarily responsible for serving GraphQL queries to consumers. It takes a query from a client, breaks it into smaller sub-queries, and executes that plan by proxying calls to the appropriate downstream subgraphs. When we started our journey, there was only Apollo Federation in the arena, and we used it. Still, now you can look at other options (e.g. Mercurius, Conductor, Hot Chocolate, Wundergraph, Hasura Remote Schemas), compare benchmarks and decide what's important and preferable for your needs. The Gateway provides a unified API for consumers while giving backend engineers flexibility and service isolation.

I'm a big fan of tRPC. It's amazing how it pushed TypeScript only stacks to the limit in terms of DX. Additionally, it made the GraphQL community aware of the limitations and tradeoffs of the Query language. At the same time, I think tRPC went through a really fast hype cycle and it doesn't look like we're seeing a massive move away from REST and GraphQL to RPC. That said, we see a lot of interest in RPC these days as we've adopted some ideas from tRPC and the old NextJS. In our BFF framework (https://wundergraph.com/) we've combined file based routing with RPC. In addition to tRPC, we're automatically generating a JSON Schema for each operation and an OpenAPI spec for the whole set of operations. People quite like this approach because you can easily share a set of RPC endpoints as an OpenAPI spec or postman collection. In addition, there are no discussions around HTTP verbs and such, there's only really queries, mutations and subscriptions. I'm curious what other people's experiences are with GraphQL, REST and RPC style APIs? What are you using these days and how many people/teams are involved/using your apis?

You can check out the source code on GitHub and leave a star if you like it. Follow me on Twitter, or join the discussion on our Discord server.

If you like the work we're doing and want to support us, give us a star on GitHub.