graphql-core VS join-monster

Compare graphql-core vs join-monster and see what are their differences.

graphql-core

A Python 3.6+ port of the GraphQL.js reference implementation of GraphQL. (by graphql-python)

join-monster

A GraphQL to SQL query execution layer for query planning and batch data fetching. (by join-monster)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
graphql-core join-monster
2 3
498 2,654
1.0% 0.7%
7.9 6.6
14 days ago about 1 month ago
Python JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

graphql-core

Posts with mentions or reviews of graphql-core. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-08.

join-monster

Posts with mentions or reviews of join-monster. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-08.
  • Understanding TTFB Latency in DJango - Seems absurdly slow after DB optimizations even locally
    4 projects | /r/django | 8 Dec 2023
    GraphQL could be efficiently translated into SQL and things certainly try, but the only thing close to a "bulletproof" implementation I found was Join Monster (https://github.com/join-monster/join-monster) in NodeJS-land and even that I think is now mostly abandoned. GraphQL as a system was built assuming random-access to data stores is ~free because that's what Facebook has, but the rest of us don't :)
  • Ask HN: Nested Resources in REST/HTTP API URLs?
    3 projects | news.ycombinator.com | 18 Aug 2022
    REST is not a strict specification and it's not a single implementation, you can just start doing it.

    That said, I wouldn't recommend going the allow everything flexible resolver way like GraphQL: it's terrible for performance (eg. most APIs use N+1 queries unless you have something like https://github.com/join-monster/join-monster), the complexity of the codebase skyrockets and having to specify all the fields you want is not exactly ergonomic in most situations.

  • GraphQL Is a Trap?
    18 projects | news.ycombinator.com | 6 May 2022