wrappers
wundergraph
wrappers | wundergraph | |
---|---|---|
11 | 108 | |
440 | 2,162 | |
3.9% | 0.5% | |
9.5 | 9.3 | |
14 days ago | 3 days ago | |
Rust | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
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.
wrappers
-
Should I Open Source my Company?
I used one of their open source work in a project: https://github.com/supabase/wrappers
It’s appreciated since SaaS on AWS is a no-no in my field.
-
SQL as API
I’m currently playing with PostgreSQL, foreign data wrappers, and pgrx rust extensions. My development experience has been surprisingly smooth and enjoyable.
My main issue is that joins will be processed locally, so all the foreign data will be fetched before the join happens. But otherwise basic CRUD is easy.
https://wiki.postgresql.org/wiki/Foreign_data_wrappers
https://github.com/pgcentralfoundation/pgrx
https://github.com/supabase/wrappers
-
Is anyone here interested in a general purpose guide on how to sync data between Supabase and outside resources?
However, considering the emergence of Supabase wrappers, it might be more beneficial to develop a walkthrough focused on creating Rust-based wrappers. This way, the community can start building a variety of useful wrappers (really plugins).
- Supabase Wrappers
-
Hasura Remote Schema analogue in Supabase
We're experimenting with including tables connected to external data sources using Supabase Wrappers https://github.com/supabase/wrappers as a way to link external APIs into the GraphQL schema but that work is in an early stage. That approach would be limited to the Stripe, Firebase and S3 for now though
-
Is it possible to directly connect Supabase to a MySQL database?
This would be an ideal use case for a postgresql foreign data wrapper. See more here: https://github.com/supabase/wrappers/
- Supabase Wrappers: A Framework for Postgres Foreign Data Wrappers
-
Supabase Wrappers: A Framework for Building Postgres Foreign Data Wrappers
> On a sidenote, is not the wrappers for Airtable, BigQuery and ClickHouse opensourced? Or why did they skip that column in the second table?
All of the wrappers are open source. You can see the source for the Airtable, BigQuery, and ClickHouse wrappers here https://github.com/supabase/wrappers/tree/5fac8afb62e6e8362b...
The `self-hosted` column is only missing from the "under development" wrappers in the blog post's table because those are not production ready and shouldn't be self hosted (yet).
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.
What are some alternatives?
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
graphql-go-tools - GraphQL Router / API Gateway framework written in Golang, focussing on correctness, extensibility, and high-performance. Supports Federation v1 & v2, Subscriptions & more.
Multicorn - Data Access Library
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
multicorn2
electric - Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.
pgsql-http - HTTP client for PostgreSQL, retrieve a web page from inside the database.
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
pg_net - A PostgreSQL extension that enables asynchronous (non-blocking) HTTP/HTTPS requests with SQL
chatgpt-raycast - ChatGPT raycast extension