swift-graphql
fquery
| swift-graphql | fquery | |
|---|---|---|
| 3 | 5 | |
| 604 | 10 | |
| - | - | |
| 6.0 | 5.9 | |
| 5 months ago | 5 months ago | |
| Swift | Python | |
| MIT License | 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.
swift-graphql
-
SwiftGraphQL - A GraphQL client for Swift lovers.
I love Swift; you love Swift; we want to do everything we can in Swift. It has a fantastic type-system and a robust compiler. We also like GraphQL. It's a neat way to construct a type-safe bridge from your server to the client. Its syntax isn't as rich as Swift's, but who cares, right? SwiftGraphQL aims to make the best of both worlds; here's how we do it.
- SwiftGraphQL - A GraphQL client that lets you forget about GraphQL.
-
SwiftGraphQL – A GraphQL client that lets you forget about GraphQL
It also generates API structs from the schema. The problem is that it's hard to reuse structures that you've generated in your application model. You can read more about the pitfalls in the F.A.Q section of the repository.
https://github.com/maticzav/swift-graphql#what-are-the-pitfa...
fquery
-
Solving the double (quintuple) declaration Problem in GraphQL Applications
Similar benefits without codegen (based on decorator magic) for a python based stack:
https://github.com/adsharma/fquery
* Use dataclasses for both database schema and the user facing operations
- Cut Out the Middle Tier: Generating JSON Directly from Postgres
- Against SQL
- Django for Startup Founders: A better software architecture for SaaS startups
-
SwiftGraphQL – A GraphQL client that lets you forget about GraphQL
Re: Conways law at Facebook
I was at Facebook when GraphQL was invented, maintaining a backend storage service where a core assumption was that storage should be reorganized based on access patterns and that predicates should be pushed down to storage where they can be executed more efficiently.
GraphQL was hard to push predicates down, because you don't know which of the edges were written in PHP.
My response was fquery[1], which is like what's being discussed here but with python as the source language instead of swift and amenable to preserving the largest possible query structure for backend optimizers, including SQL optimizers.
It has some early demos converting a GraphQL/fquery into SQL where possible. It should be possible to add enough metadata to fquery to identify if an edge is non-trivial (calls into another microservice) or trivial (can be optimized to a storage backend or SQL).
[1] https://github.com/adsharma/fquery
What are some alternatives?
apollo-ios - 📱 A strongly-typed, caching GraphQL client for iOS, written in Swift.
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
Graphaello - A Tool for Writing Declarative, Type-Safe and Data-Driven Applications in SwiftUI using GraphQL
rel8 - Hey! Hey! Can u rel8?
SociableWeaver - Build declarative GraphQL queries in Swift.
prosto - Prosto is a data processing toolkit radically changing how data is processed by heavily relying on functions and operations with functions - an alternative to map-reduce and join-groupby
WSDL2Swift - Pure Swift alternative to WSDL2ObjC making a SOAP request & parsing its response as defined in WSDL
DjangoChannelsGraphqlWs - Django Channels based WebSocket GraphQL server with Graphene-like subscriptions
pocket-ios - Mozilla's Pocket iOS App, Rebuilt in Swift
django_for_startups - Code for the book Django for Startups
jrutil
django-channels - Developer-friendly asynchrony for Django