apollo-ios VS graphql-js

GraphQL queries are just HTTP POST queries with a JSON body. They're supported everywhere.

If you want specialized tooling for them, Kotlin and Swift both have great strongly-typed GraphQL libraries.

Apollo publishes libraries for both:

- https://www.apollographql.com/docs/kotlin/

- https://www.apollographql.com/docs/ios/

apollo-ios - A strongly-typed, caching GraphQL client. Language: Swift.

RFC: apollo-ios/CodegenProposal.md at release/1.0-alpha-incubating · apollographql/apollo-ios · GitHub Example Generated Output: apollo-ios/Tests/ApolloCodegenTests/AnimalKingdomAPI/ExpectedGeneratedOutput at release/1.0-alpha-incubating · apollographql/apollo-ios · GitHub PR for discussion is here: [RFC] In Progress - Release 1.0 - Swift Codegen by calvincestari · Pull Request #1876 · apollographql/apollo-ios · GitHub

Apollo iOS, on the other hand, generates Swift types from queries in our "queries.graphql" files and supports caching out of the box. Generating types from the SDL is not per se a problem, but it becomes cumbersome and error-prone with large nested queries. Apollo iOS also strongly-binds the generated structures to your queries, making it almost impossible to translate fetched data into an internal state.

Apollo Client does have a good integration with these frameworks including React, iOS and Android — so, you might want to check that out

To begin, I'm going to start with GraphQL. This repo is a JS-specific implementation for GraphQL, for which projects written in JS/TS can utilize to build an API for their web app. The reason why I chose this project is because I've always been intrigued by how GraphQl challenges the standard way of building an API, a.k.a REST APIs. I have very little knowledge about this project since I've never used it before at work or for my personal projects. I only have theoretical knowledge about it which I gained from watching YouTube videos. It also uses TypeScript which is fascinating because type safety is very important when building software considering it cleans out a lot of bugs early on before the software is shipped.

When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.

In short, we chose not to pursue GraphQL due to some limitations with union types and a lack of support for maps. This is further detailed in this link: limitations.

benchmarks: This directory contains benchmark tests that help measure the performance of the package's code, these tests can be are very useful when experimenting with performance optimizations, and to ensure no slowdowns are introduced between releases. Example from graphql.

GraphiQL (and many other tools) relies on introspection query which AFAIK is not guaranteed to have any specific order (and many libs don't support it). Apollo Server is built on top of graphql-js and it relies on it for this functionality.

GraphQL.js + Knex.js + knex-types (TypeScript generator for Knex)

Yoga v2 supports some experimental GraphQL features such as @defer and @stream, allowing you to get a taste of the future of GraphQL (with compatible clients such as URQL).

Visitors are used for many reasons like extensibility, plugins, printing an entire schema somewhere, etc.

support for @defer and @stream