Our great sponsors
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
urql
The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
pothos
Pothos GraphQL is library for creating GraphQL schemas in typescript using a strongly typed code first approach
I consider that to be misleading selective editing. Here's a more faithful representation of that missive:
> For the back-end, Apollo Server absolutely can be beat by tools that don't require you to write any code:
> https://supabase.com/blog/pg-graphql
> https://www.graphile.org/postgraphile/
> https://hasura.io/
The careful reader will note that I presented three alternatives, with the one provided by my company last. Moreover, what I wrote is in fact a matter of fact. If you wish to have a GraphQL server without having to write server code to do it, as fine a product as Apollo is you cannot use Apollo to do it because that's not what Apollo does.
Eh, https://github.com/urql-graphql/urql is considered the improved re-architected project that doesn't contain the legacy baggage from the beginning of GraphQL like Apollo does.
Depends on language, I've build GraphQL servers in a few, though mostly JavaScript and Python. For Python I used to use Graphene, these days I use Strawberry.
For JavaScript, I originally used graphql-js and express-graphql, as these were the original libraries and I was a literal day 1 adopter. All the libraries are essentially just wrappers around graphql-js, so it's still viable to use directly. But for schema-building I now use Pothos (https://pothos-graphql.dev/), I'd probably use graphql-helix as the http layer (https://github.com/contra/graphql-helix).
Depends on language, I've build GraphQL servers in a few, though mostly JavaScript and Python. For Python I used to use Graphene, these days I use Strawberry.
For JavaScript, I originally used graphql-js and express-graphql, as these were the original libraries and I was a literal day 1 adopter. All the libraries are essentially just wrappers around graphql-js, so it's still viable to use directly. But for schema-building I now use Pothos (https://pothos-graphql.dev/), I'd probably use graphql-helix as the http layer (https://github.com/contra/graphql-helix).
Related posts
- Show HN: Graphweaver – Instant GraphQL API on Postgres, MySQL, SQLite and More
- I reviewed 1,000s of GraphQL vs. REST perspectives
- Fara job de 6 luni
- What do you guys use for a backend? I've been considering Laravel but it seems like overkill for a simple project.
- Easiest way to start with fullstack- use a tool that auto-generates the GraphQL backend for you just based on data models(WIP)