wundergraph
telefunc
wundergraph | telefunc | |
---|---|---|
108 | 11 | |
2,168 | 612 | |
0.7% | - | |
9.3 | 9.1 | |
12 days ago | 22 days ago | |
TypeScript | TypeScript | |
Apache License 2.0 | 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
- The Open-Source GraphQL Federation Solution
-
GraphQL and the Beads on a String
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...
-
GraphQL Federation Field-level Metrics 101
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.
-
You do need a technical co-founder
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.
- The Open-Source Enterprise GraphQL Federation Solution
-
The Road to GraphQL At Enterprise Scale
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.
- Show HN: Graphweaver – Instant GraphQL API on Postgres, MySQL, SQLite and More
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
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?
-
Preventing prompt injections with Honeypot functions
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.
-
Beyond Functions: Seamlessly build AI enhanced APIs with OpenAI
If you like the work we're doing and want to support us, give us a star on GitHub.
telefunc
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
Compared with tRPC: https://github.com/brillout/telefunc/issues/9
-
GraphQL vs. REST APIs: a complete guide
For JavaScript based projects TeleFunc[1] can make development way simpler by 'removing' the need for an API.
[1]: https://telefunc.com/
-
Next, Nest, Nuxt Nust?
- api routes (cloud functions) require another package (on purpose). see https://telefunc.com/ from the same maintainer
other than that, no gatchas i encountered. i would choose vite-plugin-ssr again.
-
Is there a library or a standard way of creating an interface for my api endpoints?
Another suggestion to solve your problem could be to use telefunc
-
Remote Functions. Instead of API
> My experience was that for the simplest use cases, the ergonomics were unbeatable.
Exactly.
> the “just a function” interface was a distraction and I found myself wishing for a more conventional RPC interface.
For real-time use cases, I agree. I believe functions are the wrong abstraction here for real-time. I do plan to support real-time but using a "it's just variables" abstraction instead, see https://github.com/brillout/telefunc/issues/36.
> cleverer abstractions usually mean more work overall to integrate everything and boring is better.
Yes, Telefunc's downside is that it requires a transformer. The Vite and Webpack one are reliable and used in production (using `es-module-lexer` under the hood). The hope here is that, as Telefunc's popularity grows, more and more stacks are reliably supported. Also, there is a prototype using Telefunc without a transformer at all, which works but needs polishing.
> I experimented with a higher-magic version of this a couple of years ago.
Neat, curious, is it on GitHub?
-
End-to-end type safety with tRPC (example repository)
An alternativeto tRPC that I find easier to use is telefunc
What are some alternatives?
graphql-go-tools - GraphQL Router / API Gateway framework written in Golang, focussing on correctness, extensibility, and high-performance. Supports Federation v1 & v2, Subscriptions & more.
electron-trpc - Build type-safe Electron inter-process communication using tRPC
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
vike - 🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
electric - Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.
tRPC-example - e2e type safety with tRPC
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
ts-websocket-compressor - This library compresses data sent over a WebSocket connection to improve throughput on devices that can't use compression for one reason or another.
Multicorn - Data Access Library
phero - Full-stack type-safety with pure TypeScript
chatgpt-raycast - ChatGPT raycast extension
openapi-typescript-codegen - NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification